ci: fix semantic-release configuration naming #538
Merged
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
|
Terraform Plan Changes Terraform Plan: 0 to be created, 0 to be deleted, 1 to be updated, 0 to be replaced, 5 unchanged.Resources to update! azurerm_linux_web_app.gratibot_app_service |
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.
The previous change to the name of this file seems to be unnecessary after testing locally. The previous name of the file (
release.config.js) at the root of the directory appears to work. However, the official semantic-release release notes (https://github.com/semantic-release/semantic-release/releases/tag/v23.0.0) seem to indicate that it should not work. Instead of reverting, I've chosen to move to an alternate name that should also work. This.releaserc.jsis mentioned as an option in all the documentation, and appears to be picked up when dry running locally.