Skip to content
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

Renaming package references breaks auto-release-creation and channel version rules #4953

MJRichardson opened this issue Oct 8, 2018 · 2 comments


Copy link

commented Oct 8, 2018

When using script step package references (introduced in Octopus 2018.8) for auto-release-creation or channel-version-rules, the package-reference name is used. If the package-reference is re-named, these rules no longer work as expected.

We will add an ID field to the package-references, and use this rather than the name. Re-naming the package-reference will still break any external references (build-server plugins, etc), but we warn about this.


This comment has been minimized.

Copy link

commented Oct 23, 2018

Release Note: In 2018.8 it was possible to corrupt auto-release-creation and channel rules by renaming package references on script steps


This comment has been minimized.

Copy link

commented Jan 21, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.