bobheadxi/deployments@v1 #82
bobheadxi
announced in
Announcements
Replies: 1 comment
-
|
The |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
bobheadxi/deployments@v1is now available! This release brings a streamlined API, refactored codebase (now complete with integration testing), and more reliable behaviour. Thank you to everyone who has used this action and contributed features, documentation, and more!v0.6.x- please migrate with care! If you run into any issues, please feel free to request help in GitHub discussions:no_overrideis nowoverride, and the default behaviour isoverride: trueinstep: finish(step: startbehaviour remains unchanged, but you can now setoverride: trueon it now as well).log_argsis nowdebug, but does the same thing as before.envis now always required. You can useenv: ${{ steps.deployment.outputs.env }}to avoid repeating your env configuration.REMOVED:This was added back in https://github.com/bobheadxi/deployments/releases/tag/v1.0.1.auto_inactive- useoverrideinstead.transient- all deployments created by this action aretransientby default, with removals handled byoverrideorstep: deactivate-env.step: delete-envdeletes an environment entirely.Then you can change your workflow to target the
v1tag, and automatically receive updates going forward:To preserve old behaviour, please ensure that you have your usage of
bobheadxi/deploymentspinned to the desired version.This discussion was created from the release bobheadxi/deployments@v1.
Beta Was this translation helpful? Give feedback.
All reactions