chore(deps): update bobheadxi/deployments action to v1 #116
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
e.g. postgres database for the api tests.
… linter Exclude packages which only start the lint process like "@vue/cli-plugin-eslint", "lint-staged" Regex was tested here: https://regex101.com/r/rGeHCu/1
Pull Request Test Coverage Report for Build 2179867651
💛 - Coveralls |
Pull Request Test Coverage Report for Build 2302889074
💛 - Coveralls |
renovate
bot
force-pushed
the
renovate/bobheadxi-deployments-1.x
branch
from
e46c086 to
a72805f
Compare
Pull Request Test Coverage Report for Build 2179867651Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.6.2->v1.2.0Release Notes
bobheadxi/deployments
v1.2.0Compare Source
What's Changed
delete-envwork as documented by @awesomeunleashed in https://github.com/bobheadxi/deployments/pull/101${{ github.token }}by @mxcl in https://github.com/bobheadxi/deployments/pull/102New Contributors
Full Changelog: bobheadxi/deployments@v1...v1.2.0
v1.1.0Compare Source
See https://github.com/bobheadxi/deployments/releases/tag/v1.0.0 for more details about what's new in
bobheadxi/deployments@v1and how to migrate fromv0.6.x!This release adds the ability to provide the
payloadparameter for deployment creation onstep: start(https://github.com/bobheadxi/deployments/pull/87)v1.0.1Compare Source
See https://github.com/bobheadxi/deployments/releases/tag/v1.0.0 for more details about what's new in
bobheadxi/deployments@v1and how to migrate fromv0.6.x!This release adds back the
auto_inactiveoption that was originally removed.v1.0.0Compare Source
bobheadxi/deployments@v1brings 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.auto_inactive- useoverrideinstead.~~ This was added back in https://github.com/bobheadxi/deployments/releases/tag/v1.0.1.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.Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.