Skip to content

Conversation

kichristensen
Copy link
Contributor

@kichristensen kichristensen commented May 17, 2025

Changes

  • Modified PublishExample function to publish example bundles with both version-specific and latest tags
  • Added error handling for the first publish operation

closes 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.

…publish with latest tag. Updated command to publish example bundle with an additional step for tagging.

Signed-off-by: Kim Christensen <[email protected]>
…roved consistency in mixin installations.

Signed-off-by: Kim Christensen <[email protected]>
… improve reliability of mixin installations.

Signed-off-by: Kim Christensen <[email protected]>
Copy link
Member

@dgannon991 dgannon991 left a 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")
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Member

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?

Copy link
Contributor Author

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

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

Successfully merging this pull request may close these issues.

(bug): Unable to pull bundles with latest tag
2 participants