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'm a maintainer of semantic-release and I noticed you are using a quite old version. The last version is
15.9.16
!It seems you have a Travis job only for running semantic-release, but all your tests run on Azure Pipeline. semantic-release now works on pretty much any CI, so I removed the Travis config and added a new job on Azure Pipelines that runs semantic-release once all the test are successful.
In order to complete the config you should create 2 secured environment variable on Azure Pipeline:
GH_TOKEN
set with a GitHub personal tokenNPM_TOKEN
set with an npm token (only theauth-only
level of npm two-factor authentication is supported)I never used Azure Pipeline before, so any review and feedback on my changes there would be much appreciated!