Momo Kornher

Good observation! The untidiness aside, do you experience any issues with this?

Yeah, we should!

How about the `prerelease` option? Any reasons that's not suitable for your use case?

> I want to be able to generate ad hoc pre-releases when testing a release. I don't want ALL releases to be a pre-release. Understood. Treating this as a feature...

Hi thanks for reporting this. I can't reproduce this with plain `@jsii/spec`. `ajv` is used to validate assemblies of dependencies. So if your Project B depends on Project A, when...

> This may or may not be relevant, but in Project A I got a big warning message when upgrading stating that I should use jsii rosetta version 5 instead...

Hm, that still doesn't really explain the `ajv` issue. You could try deleting `yarn.lock` and `node_modules` and then run `yarn install` in Project B. --- The change in the jsii...

> Regarding the jsii/docgen version, this dependency (and version) is added by projen. That's correct. It currently doesn't mandate the version used for jsii-docgen though and if you project is...

Change the version number in `package.json` - But since your project is new. What version is `jsii-docgen` currently on?

Hi @abdsahin Can you confirm the scenario with you. Do I understand this correctly, with this PR merged, if the release workflow (or task) is run multiple times in a...