chore(main): release 0.2.0 - #13
Merged
Merged
Conversation
NickJosevski
added a commit
that referenced
this pull request
Aug 22, 2026
Releasing 1.0.0 (#13) is blocked by a failing Lint check, and the cause is this workflow, not the release. The sed used `.*` after `create-release#`, which also consumed the trailing colon of the YAML mapping key: - OctopusDeploy/create-release#v0.1.1: -> - OctopusDeploy/create-release#v1.0.0 Every example then had an unkeyed sequence entry followed by indented mappings, so the plugin linter fails with "bad indentation of a sequence entry". The bug has been here since the workflow was added; it simply never ran, because there has been no release since 2022. The replacement matches only the version and always re-emits the colon, so it is also self-healing on a README a previous run already mangled. It still leaves other plugins' refs (e.g. octopus-login#) alone. Also adds a concurrency group. release-please pushed to the release branch three times in quick succession, and the three resulting runs raced on git push; one failed with "! [rejected] ... (fetch first)". Verified by running the new sed over main's README and linting the result: 7 examples valid, no YAML errors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
NickJosevski
force-pushed
the
release-please--branches--main
branch
from
August 22, 2026 02:07
eaa7cf1 to
b9cfaa6
Compare
team-modern-deployments-bot
force-pushed
the
release-please--branches--main
branch
from
August 24, 2026 23:49
b9cfaa6 to
a3de4fe
Compare
NickJosevski
added a commit
that referenced
this pull request
Aug 26, 2026
Releasing 1.0.0 (#13) is blocked by a failing Lint check, and the cause is this workflow, not the release. The sed used `.*` after `create-release#`, which also consumed the trailing colon of the YAML mapping key: - OctopusDeploy/create-release#v0.1.1: -> - OctopusDeploy/create-release#v1.0.0 Every example then had an unkeyed sequence entry followed by indented mappings, so the plugin linter fails with "bad indentation of a sequence entry". The bug has been here since the workflow was added; it simply never ran, because there has been no release since 2022. The replacement matches only the version and always re-emits the colon, so it is also self-healing on a README a previous run already mangled. It still leaves other plugins' refs (e.g. octopus-login#) alone. Also adds a concurrency group. release-please pushed to the release branch three times in quick succession, and the three resulting runs raced on git push; one failed with "! [rejected] ... (fetch first)". Verified by running the new sed over main's README and linting the result: 7 examples valid, no YAML errors. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
team-modern-deployments-bot
force-pushed
the
release-please--branches--main
branch
from
August 26, 2026 05:01
26638e5 to
028afa5
Compare
team-modern-deployments-bot
changed the title
team-modern-deployments-bot
force-pushed
the
release-please--branches--main
branch
from
August 26, 2026 05:01
028afa5 to
be51f56
Compare
NickJosevski
added a commit
that referenced
this pull request
Aug 26, 2026
release-please opened #13 proposing 1.0.0, because bump-minor-pre-major defaults to false and a breaking change therefore takes 0.x straight to 1.0.0. We want to keep iterating on 0.x, so set it to true: pre-1.0.0 breaking changes now produce a minor bump, making the octo -> octopus migration 0.2.0 rather than 1.0.0. Also corrects the version numbers the migration docs promise, which were written assuming a 1.0.0 release: "changed in v1" -> "changed in 0.2.0", and "Migrating from v0.x" -> "Migrating from 0.1.x" with its anchor. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
team-modern-deployments-bot
force-pushed
the
release-please--branches--main
branch
from
August 26, 2026 23:01
b4fcd60 to
239488d
Compare
team-modern-deployments-bot
force-pushed
the
release-please--branches--main
branch
from
August 28, 2026 00:33
b8872b6 to
05c12ea
Compare
NickJosevski
approved these changes
Aug 28, 2026
Contributor
|
🤖 Created releases: 🌻 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
🤖 I have created a release beep boop
0.2.0 (2026-08-28)
⚠ BREAKING CHANGES
api_keynow takes the API key itself rather than the name of an environment variable to eval.what_if,packages_folderandpackage_prereleaseare rejected, because the octopus CLI has no equivalent and silently ignoring them would change what a build does. config_file, log_level, timeout, proxy, proxy_username, proxy_password and ignore_ssl_errors warn and are ignored. OCTOPUS_CLI_SERVER and OCTOPUS_CLI_API_KEY are no longer read.Features
Bug Fixes
This PR was generated with Release Please. See documentation.