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

Investigate a method for versioning builders #20

Open
jthegedus opened this issue Nov 14, 2019 · 2 comments
Open

Investigate a method for versioning builders #20

jthegedus opened this issue Nov 14, 2019 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@jthegedus
Copy link
Owner

I don't want to use the latest tag exclusively in case of a bad update. What methods could be used to version these?

@jthegedus jthegedus added the enhancement New feature or request label Nov 14, 2019
@jthegedus jthegedus self-assigned this Nov 14, 2019
@dbrtly
Copy link

dbrtly commented Jun 26, 2024

Should the custom-builders.yaml file include a sha256 key with value matching a specific commit?

@jthegedus
Copy link
Owner Author

jthegedus commented Jun 26, 2024

Yes, I think that would be the ideal method. Should probably also support a "major" version as has become the trend with GitHub Actions, so people can use builder@1 and automatically get the latest for that major version... not sure.

It becomes a question of ease-of-use vs what is the most secure. Given no dependabot support, a builder which runs and checks builder versions would also be useful. Or just get https://github.com/sethvargo/ratchet to support meta-builders (if it even needs changes to 🤔)

What I described above are called "versioned" (sha) and "unversioned" (major semver #) in Ratchet - https://github.com/sethvargo/ratchet#terminology

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants