Skip to content

chore: explicit version bump for release #648

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

Merged
merged 1 commit into from
Jul 13, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion codebuild/release/prod-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ env:
variables:
NODE_OPTIONS: "--max-old-space-size=4096"
BRANCH: "master"
# An explicit version bump
VERSION_BUMP: ""
secrets-manager:
OTP_SECRET_KEY: npm/aws-crypto-tools-ci-bot/2FA:OTP_SECRET_KEY
NPM_TOKEN: npm/aws-crypto-tools-ci-bot/2FA:NPM_TOKEN
Expand Down Expand Up @@ -31,7 +33,7 @@ phases:
# Publish to a local verdaccio server and run all tests against it
- npm run verdaccio
# Generate new version and CHANGELOG entry and push it
- npx lerna version --conventional-commits --git-remote origin --yes
- npx lerna version --conventional-commits --git-remote origin --yes ${VERSION_BUMP:+$VERSION_BUMP --force-publish}
# Log the commit for posterity
- git log -n 1
# Extract the otp using the secrets environment variables from above.
Expand Down