-
Notifications
You must be signed in to change notification settings - Fork 245
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
feat(pacmak): prerelease identifier support #2146
Conversation
When an NPM package built with `jsii` is tagged with a version that includes a prerelease identifier (e.g: `1.2.3-alpha.1`), automatically represent this as a pre-release version in generated packages, too. For most currently supported languages, this simply means forwarding the version untouched, however for Python, prerelease identifiers need to be mapped into one of the supported tokens in PyPI (`.dev#`, `.a#`, `.b#` or `.rc#`). Fixes #2114
Co-authored-by: Niranjan Jayakar <nija@amazon.com>
…muller/auto-preversions
…t (who also replaces 'fs' for it's own needs)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main concern is about post releases.
The configuration for `jsii` is recorded in the `package.json` file, which is the standard package manifest for NPM | ||
packages. This document describes the constraints and extensions `jsii` adds to the [package.json schema]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(for the future) prefer wholesale adjustments and refactors to be separate PRs, hence separate commits 😉
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah this is auto-format-on-save... -_-
Thank you for contributing! ❤️ I will now look into making sure the PR is up-to-date, then proceed to try and merge it! |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
When an NPM package built with
jsii
is tagged with a version thatincludes a prerelease identifier (e.g:
1.2.3-alpha.1
), automaticallyrepresent this as a pre-release version in generated packages, too. For
most currently supported languages, this simply means forwarding the
version untouched, however for Python, prerelease identifiers need to
be mapped into one of the supported tokens in PyPI (
.dev#
,.a#
,.b#
or.rc#
).Fixes #2114
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.