chore: fix candidate bump invocation

[iliapolo]

Allow versions with pre-release tags in stable branches to allow BUMP_CANDIDATE to work. Otherwise, after the bump, any call to resolve-version will fail because there is a mismatch between the actual version and release.json.

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[gitpod-io]

[iliapolo]

@eladb There was a bug in the changelog skip directive.

Even after fixing that, there is an error when running the bump-candidate.sh script:

/private/tmp/aws-cdk/aws-cdk-master/scripts/resolve-version-lib.js:47
      throw new Error(`found pre-release tag in version specified in ${versionFile} is ${currentVersion} but "releaseType"" is set to "stable"`);
      ^

Error: found pre-release tag in version specified in version.v1.json is 1.72.0-rc.0 but "releaseType"" is set to "stable"

I imagine we can just disable this check in case its a testing execution? Not sure what the implications of that though.

Feel free to take over this branch.

[mergify]

Title does not follow the guidelines of Conventional Commits. Please adjust title before merge.

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

[aws-cdk-automation]

AWS CodeBuild CI Report

• CodeBuild project: AutoBuildProject6AEA49D1-qxepHUsryhcu
• Commit ID: a231b8e
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[mergify]

Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).