![]() › ✔ Completed step "generateNotes" of plugin AM] › ℹ Start step "prepare" of plugin AM] › ℹ Update /home/circleci/project/README. Semantic-release:release-notes-generator commit: 'commits' +0ms Semantic-release:release-notes-generator issue: 'issue' +0ms Semantic-release:release-notes-generator linkReferences: undefined +0ms Semantic-release:release-notes-generator host: '' +0ms Semantic-release:release-notes-generator currentTag: 'v1.0.0-next.2' +0ms Semantic-release:release-notes-generator previousTag: 'v1.0.0-next.1' +0ms Semantic-release:release-notes-generator repository: 'ui_kit' +0ms Semantic-release:release-notes-generator owner: 'monarc_dev' +0ms Semantic-release:release-notes-generator host: undefined +0ms › ℹ Start step "generateNotes" of plugin version: '1.0.0-next.2' +0ms › ✔ Completed step "analyzeCommits" of plugin AM] › ℹ The next release version is 1.0.0-next.2 › ℹ Analysis of 2 commits complete: minor release › ℹ The release type for the commit is minor "branches": ["stable", match commit with release type 'minor' +0ms Semantic-release "^9.0.1", CI environment: I have the following version set in my development branch package.jsonĪlso my version is not being incremented in package.json as it did when I was running it locally, for any of the branches.Įxpected behaviour would to have the pre-release version increment as per normal, also have my package.json update. 1 Is there any best practices when using python distributions in along with releases with Git Tagging My concern is SHOULD you bump distribution version in situations where files outside project is updated but semantic versioned git tag is incremented. If I then make a pull request for our "development" branch into our "stable" release branch, it updates the versions correct as it should, for example v1.1.0 gets released. However, another feat commit doesnt increment the version to v1.1.0-next.1. Once we are happy with how it looks etc, we then merge our "development" branch into our "stable.įirst push for "next" creates a tag called v1.0.0-next.1. This is a brand new project, so fresh versions etc.Ĭurrently have a pre-release branch called "next", release branch called "stable", all features all worked on in our "development" branch and they have the correct feat(test): this is a test commit messages.įrom the development branch we create a pull request into "next".
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |