Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Update canary version namings #7661

Closed
shuse2 opened this issue Oct 19, 2022 · 0 comments · Fixed by #7683
Closed

Update canary version namings #7661

shuse2 opened this issue Oct 19, 2022 · 0 comments · Fixed by #7683
Assignees
Milestone

Comments

@shuse2
Copy link
Collaborator

shuse2 commented Oct 19, 2022

Expected behavior

Canary version should be named v6.0.0-canary.xxxxx.

Actual behavior

Canary version will create v6.0.0-alpha.35728289, where it conflicts with semver for alpha.3 or alpha.4

@shuse2 shuse2 self-assigned this Oct 24, 2022
@shuse2 shuse2 added this to the Sprint 81 milestone Oct 24, 2022
shuse2 added a commit that referenced this issue Oct 27, 2022
### What was the problem?

This PR resolves #7661 

### How was it solved?

- Update jenkins job to use `--preid` flag

### How was it tested?

- Once this is merged, we need to check the npm.lisk.com
ishantiw pushed a commit that referenced this issue Nov 15, 2022
### What was the problem?

This PR resolves #7661 

### How was it solved?

- Update jenkins job to use `--preid` flag

### How was it tested?

- Once this is merged, we need to check the npm.lisk.com
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant