-
Notifications
You must be signed in to change notification settings - Fork 28
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore!: standardize flavors, bundle dir and ghcr namespace (#933)
## BREAKING CHANGES - LeapfrogAI `latest` UDS bundles on `main` branch will break when this is merged unless the following is done: - add `-upstream` to all components in `latest` bundles - change namespace of the referenced repository to `packages/uds/leapfrogai` - release-please does not currently work with flavors as it is currently configured to follow SemVer standards; manual changing of the `latest` bundles ref must be done moving forward until a fix (custom replacement strategy) is implemented ## CHANGES - Moves bundles to UDS Common standard directory (`bundles/`) - Shifts the target GHCR repository sub-directory from `packages/leapfrogai` to `packages/uds/leapfrogai` as part of the[ _Made For UDS_](https://github.com/defenseunicorns/uds-common/blob/main/docs/uds-package-practices.md) standard - Adds `-upstream` as the default bundle ref and increments the ref manually ## NOTES After 0.12.0 is released and artifacts are published, PR #977 should be merged in to add the UDS bundle manifest pointers necessary to use the `upstream` flavor and v0.12.0 in general.
- Loading branch information
1 parent
020dc07
commit 985642a
Showing
13 changed files
with
33 additions
and
57 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters