-
Notifications
You must be signed in to change notification settings - Fork 8
Publish Examples with Latest Tag #30
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
base: main
Are you sure you want to change the base?
Conversation
…publish with latest tag. Updated command to publish example bundle with an additional step for tagging. Signed-off-by: Kim Christensen <[email protected]>
8cf397a
to
5a9a587
Compare
…roved consistency in mixin installations. Signed-off-by: Kim Christensen <[email protected]>
… improve reliability of mixin installations. Signed-off-by: Kim Christensen <[email protected]>
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.
Only one thought, happy to be told it's not worth it!
return porter.EnsureMixin(mixin) | ||
}) | ||
} | ||
return errG.Wait() | ||
} | ||
|
||
func EnsurePorter() { | ||
porter.EnsurePorter() | ||
porter.EnsurePorterAt("v1.2.1") |
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.
Is it worth updating the DefaultPorterVersion
variable instead?
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.
@dgannon991 Yes we probably should, but it requires the magefiles repository to be updated. I will create a PR for that, but I think it make sense to do it here for now to unblock.
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.
@kichristensen Sorry, I know it's my fault, but is it worth changing this to 1.3.0?
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.
@dgannon991 Good point :) I have just merged the update to magefiles, with should change the default version to 1.3.0, so this can be removed again, I will do that once the magefiles release have been created
Changes
PublishExample
function to publish example bundles with both version-specific and latest tagscloses getporter/porter#3020
Why
This change ensures that example bundles are available with both version-specific tags and a
latest
tag, making it easier for users to reference the most recent version of examples while maintaining version history.Impact
This change improves the usability of example bundles by providing a consistent way to reference the latest version while maintaining version history.