Conversation
…l for visibility BREAKING CHANGE: the visibility prompt no longer returns `Public` or `Private` but instead returns whether the contribution model is open-source (OSS), inner-source (ISS), or closed-source (CS) for form8ion/project#1472
…d v23 BREAKING CHANGE: the minimum supported node version is now v22.21
chore(action): pin form8ion/semantic-release-workflow action to 19ce8e3 (beta)
…c-release-workflow-2.x chore(action): update form8ion/semantic-release-workflow action to v2.0.1 (beta)
chore(deps): update dependency ls-engines to v0.10.0 (beta)
…r-12.x chore(deps): update dependency @cucumber/cucumber to v12 (beta)
chore(deps): update dependency chai to v6 (beta)
… question was a valid choice BREAKING CHANGE: providing an invalid answer to the visibility question will now fail validation
…orepo chore(deps): update vitest monorepo to v4 (beta)
…orepo fix(deps): update dependency joi to v18 (beta)
…int-config-2.x chore(deps): update dependency @form8ion/commitlint-config to v2.0.15 (beta)
chore(deps): update dependency publint to v0.3.21 (beta)
BREAKING CHANGE: logger is now required as a dependency to the `applyEnhancers` method
BREAKING CHANGE: the dependencies object is now required for `applyEnhancers` and must include a logger instance
|
🎉 This PR is included in version 5.0.0-beta.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 5.0.0-beta.8 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 5.0.0-beta.9 🎉 The release is available on: Your semantic-release bot 📦🚀 |
to enable injecting dependencies, like the logger
|
🎉 This PR is included in version 5.0.0-beta.10 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…projects since this list should be a list of OSI approved licenses, it should not be presented to non-OSS projects. projects of other visibilities can have licenses, but should not be OSI licenses, so handling those cases better should be handled as a later enhancement BREAKING CHANGE: the license choice prompt is no longer presented to non-OSS projects. handling license choice for other project types may be added at a later time
|
🎉 This PR is included in version 5.0.0-beta.11 🎉 The release is available on: Your semantic-release bot 📦🚀 |
…question is for OSS projects BREAKING CHANGE: the license prompt now only presents OSI approved options since the question is only presented for OSS projects
|
🎉 This PR is included in version 5.0.0-beta.12 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 5.0.0-beta.13 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
js-yamlwithyamlproject-corePossible details to move to project core:
questionsForBaseDetailsvisibilityOptions