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!: standardize flavors, bundle dir and ghcr namespace #933

Merged
merged 15 commits into from
Sep 4, 2024

Conversation

justinthelaw
Copy link
Contributor

@justinthelaw justinthelaw commented Aug 19, 2024

OVERVIEW

Moves bundles to UDS Common standard directory and shifts the target GHCR repository sub-directory from packages/leapfrogai to packages/uds/leapfrogai as part of the Made For UDS standard

Moving 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 the latest bundles must point to the correct flavor as published by uds 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 the upstream flavor and v0.12.0 in general.

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 standard
  • Adds -upstream as the default bundle ref and increments the ref manually

@justinthelaw justinthelaw added dependencies Pull requests that update a dependency file tech-debt Not a feature, but still necessary labels Aug 19, 2024
@justinthelaw justinthelaw requested a review from a team as a code owner August 19, 2024 17:46
@justinthelaw justinthelaw linked an issue Aug 19, 2024 that may be closed by this pull request
Copy link

netlify bot commented Aug 19, 2024

Deploy Preview for leapfrogai-docs canceled.

Name Link
🔨 Latest commit 7e27b2f
🔍 Latest deploy log https://app.netlify.com/sites/leapfrogai-docs/deploys/66d873f520a8ad0008adb189

@justinthelaw justinthelaw added the blocked 🛑 Something needs to happen before this issues is worked label Aug 19, 2024
@justinthelaw justinthelaw self-assigned this Aug 19, 2024
@justinthelaw
Copy link
Contributor Author

Post message to #leapfrogai about this breaking change ahead of time.

@justinthelaw justinthelaw changed the title chore!: standardize bundle location and moves ghcr repository chore!: standardize bundle locations and flavoring Aug 30, 2024
@justinthelaw justinthelaw changed the title chore!: standardize bundle locations and flavoring chore!: standardize flavors, bundle dir and ghcr namespace Aug 30, 2024
@justinthelaw
Copy link
Contributor Author

Relies on #920

@justinthelaw justinthelaw force-pushed the 703-chorerelease-correct-ghcr-repository-directory branch from a323ab6 to e9df4e5 Compare September 3, 2024 18:25
YrrepNoj
YrrepNoj previously approved these changes Sep 3, 2024
Copy link
Member

@YrrepNoj YrrepNoj left a 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.

bundles/latest/cpu/uds-bundle.yaml Outdated Show resolved Hide resolved
@justinthelaw justinthelaw removed the blocked 🛑 Something needs to happen before this issues is worked label Sep 3, 2024
@justinthelaw justinthelaw linked an issue Sep 3, 2024 that may be closed by this pull request
@justinthelaw justinthelaw merged commit 985642a into main Sep 4, 2024
29 of 31 checks passed
@justinthelaw justinthelaw deleted the 703-chorerelease-correct-ghcr-repository-directory branch September 4, 2024 17:21
barronstone added a commit to defenseunicorns/uds-security-hub-v1-archive that referenced this pull request Sep 9, 2024
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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file tech-debt Not a feature, but still necessary
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore(release): correct ghcr repository directory
3 participants