You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the version field in package.json contains a pre-release suffix, JSII should treat the suffix as a pre-release identifier and create pre-release versions appropriate for the package managers of the target languages.
For example, if version is specified as 2.0.0-alpha.1, it must automatically detect that this is a pre-release version and create target versions as 2.0.0-alpha.1 for Maven Central, 2.0.0-alpha.1 for Nuget and 2.0.0.a1 for PyPI.
Some package managers are restrictive in what is acceptable pre-release versions. For example, PyPI only allowsdevN, aN, bN and rcN (where N is the pre-release version number) as valid pre-release versions.
For this reason, when enabled for these package managers, it must make reasonable assumptions about allowed pre-release identifiers, erring if a pre-release identifier cannot be translated and allow overriding them in the jsii section.
The text was updated successfully, but these errors were encountered:
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
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>
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
🚀 Feature Request
Affected Languages
TypeScript
orJavascript
Python
Java
C#
,F#
, ...)Description
We would like to release the the next major version of
aws-cdk
and theconstructs
librariesinitially as pre-release. See cdk pre-release identifiers and
constructs
pre-release identifier.JSII packing needs to natively support this.
Proposed Solution
If the
version
field inpackage.json
contains a pre-release suffix, JSII should treat the suffix as a pre-release identifier and create pre-release versions appropriate for the package managers of the target languages.For example, if
version
is specified as2.0.0-alpha.1
, it must automatically detect that this is a pre-release version and create target versions as2.0.0-alpha.1
for Maven Central,2.0.0-alpha.1
for Nuget and2.0.0.a1
for PyPI.Some package managers are restrictive in what is acceptable pre-release versions. For example, PyPI only allows
devN
,aN
,bN
andrcN
(whereN
is the pre-release version number) as valid pre-release versions.For this reason, when enabled for these package managers, it must make reasonable assumptions about allowed pre-release identifiers, erring if a pre-release identifier cannot be translated and allow overriding them in the
jsii
section.The text was updated successfully, but these errors were encountered: