-
Notifications
You must be signed in to change notification settings - Fork 75
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
v11.0.0 - GitHub Release Based Deployment #111
Conversation
Your development orb has been published. It will expire in 30 days. |
Your development orb has been published. It will expire in 30 days. |
Your development orb has been published. It will expire in 30 days. |
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!
Your development orb has been published. It will expire in 30 days. |
Your development orb has been published. It will expire in 30 days. |
Your development orb has been published. It will expire in 30 days. |
…:skip] This reverts commit 6da5efa.
Description
Orb tools 11 is a ground-up rewrite of the orb, designed to be more streamlined, easier to use, utilizing the latest CircleCI features, and most importantly improves the release process to not only publish the orb on the Orb Registry but also create and tag a Release on GitHub.com.
Context: For those coming to this PR for the first time, this orb is used within CircleCI pipelines to streamline the process of writing and testing your own orbs.
Notable changes:
dev:alpha
tagged version of the orb for testing. Due to "dev" tags on CircleCI being ephemeral with a 90-day life span, if it had been over 90 days since the orb was last published this would result in an error in the CircleCI pipeline. Users would have to manually publish their orb locally to re-start the ci pipelineMigration
View the included MIGRATION.md