-
Notifications
You must be signed in to change notification settings - Fork 29
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!: standardize flavors, bundle dir and ghcr namespace #933
chore!: standardize flavors, bundle dir and ghcr namespace #933
Conversation
✅ Deploy Preview for leapfrogai-docs canceled.
|
Post message to #leapfrogai about this breaking change ahead of time. |
Relies on #920 |
a323ab6
to
e9df4e5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I did open a pondering question to see if we might want to keep our main-latest-bundles buildable.
I think I am leaning towards keeping main buildable and opening a new PR with the change in namespace when we get closer to releasing and I'm curious what others might think.
LeapfrogAI v0.12.0 included a breaking change which updated the directory structure to comply with the Made for UDS standard. Reference: defenseunicorns/leapfrogai#933 This PR updates the paths in leapfrogai_names.txt accordingly. It also removes the `rag` package, which is no longer relevant, and adds the `supabase` package to the list. Signed-off-by: Barron Stone <[email protected]>
OVERVIEW
Moves bundles to UDS Common standard directory and shifts the target GHCR repository sub-directory from
packages/leapfrogai
topackages/uds/leapfrogai
as part of the Made For UDS standardMoving forward, our packages will be published at a different sub-directory, so at the next release, all bundles must be updated to reflect these.
Additionally, as packages will be by-default published with a flavor of
upstream
thelatest
bundles must point to the correct flavor as published byuds zarf package publish
. Zarf publishing will append-${FLAVOR}
to the package when it is uploaded to the registry, and the bundle must use the correct ref. Due to this, 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 theupstream
flavor and v0.12.0 in general.BREAKING CHANGES
latest
UDS bundles onmain
branch will break when this is merged unless the following is done:-upstream
to all components inlatest
bundlespackages/uds/leapfrogai
latest
bundles ref must be done moving forward until a fix (custom replacement strategy) is implementedCHANGES
bundles/
)packages/leapfrogai
topackages/uds/leapfrogai
as part of the Made For UDS standard-upstream
as the default bundle ref and increments the ref manually