Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[chore]:Reuse API update - Migration from dep5 file to TOML file. #920

Merged
merged 1 commit into from
Mar 25, 2025

Conversation

sap-ospo-bot
Copy link
Contributor

The PR is fixing and updating the Reuse compliance to match the recent Reuse API Specification - we remove the dep5 file and migrate to the toml file. For more details please read the Reuse Specification

Copy link

changeset-bot bot commented Mar 24, 2025

⚠️ No Changeset found

Latest commit: 9926b47

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@nlunets
Copy link
Member

nlunets commented Mar 25, 2025

Should we change something build wise @ajinkyapatil8190 ?

@ajinkyapatil8190
Copy link
Member

From build wise, only the file changes from a dep5 to .toml so in the build pipeline if you use the dep5 file then please update that, else rest of the things from the reuse end stays as is.

@ajinkyapatil8190 ajinkyapatil8190 merged commit 25e84df into main Mar 25, 2025
12 of 13 checks passed
@ajinkyapatil8190 ajinkyapatil8190 deleted the Reuse-Migration-TOML-Branch branch March 25, 2025 17:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants