New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Continious Deploy to NPM with @next tag when the MINOR version number is odd(in developing branch) #1158

Closed
huan opened this Issue Apr 21, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@huan
Copy link
Member

huan commented Apr 21, 2018

According to #905, when the minor version number in semvar is odd, it means it comes from a developing branch, and it's very like UNSTABLE.

odd Examples: (UNSTABLE, in developing)

  • 0.15.1
  • 0.15.2
  • 1.1.1
  • 1.1.2

even Examples: (STABLE, production)

  • 0.16.1
  • 0.16.2
  • 1.0.1
  • 1.0.2

At the same time, we publish all the version to NPM when the code base passed the Automatic Testing by Travis CI.

We should only publish to NPM via CI/CD for the STABLE/PROD version for master branch, which means we should limit it to the version number is even.

See Also

@huan huan added the enhancement label Apr 21, 2018

@huan huan changed the title Continious Deploy to NPM with @next tag when the version number is odd(in developing branch) Continious Deploy to NPM with @next tag when the MINOR version number is odd(in developing branch) Apr 21, 2018

huan added a commit that referenced this issue Apr 21, 2018

huan added a commit that referenced this issue Apr 21, 2018

@huan

This comment has been minimized.

Copy link
Member Author

huan commented Apr 23, 2018

Done.

wechaty/.travis.yml

Lines 48 to 53 in 5fcaa39

- stage: deploy
script:
- echo "Deploying to NPM ..."
- npm version
- if ./scripts/development-release.ts; then ./scripts/package-public-config-tag-next.ts; fi
- npm run dist

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment