Closed haani-niyaz closed 2 years ago
completed
After downgrading, the new releases are no longer being created with every merge to the main branch. Is this something that will start after the first major release of v1.0.0 or is there some other issue in the workflow? @haani-niyaz
@shukra-in-spirit this is by design. semantic-release requires a commit message convention to be followed to trigger releases. I was planning on sharing this with the team today to cover this:
The release
v1.0.0
was automatically tagged via the semantic-release workflow when it was merged to master (semantic-release default start tag isv1.0.0
).v1.0.0
represents a stable production ready release and this repo isn't there yet. We should downgrade the release tov0.1.0
as it better represents the state of the repo.Actions required:
v1.0.0
release and tagv0.1.0
via UI