Ci - Add ChangeSet #3
Merged
Conversation
This file contains 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
This commit introduces a new .npmrc file with default configurations. It includes uptions to auto-install peer dependencies, dedupe peer dependents, set an empty save-prefix, mark the default tag as 'latest', and set the node-linker as 'isolated'.
All the changes to pnpm-lock.yaml in this commit are package additions that center around '@changesets/cli' package. The dependencies included are for '@changesets/cli', '@babel', and several utilities, including 'string-width', 'strip-ansi', 'wrap-ansi', and 'cliui'. The commit also includes several relevant '@types' packages. Signed-off-by: Giovanni Ravalico <[email protected]>
The changes introduce a new configuration file and README for the changeset package. These files provide the initial setup and documentation for using the `@changesets/cli` build tool for versioning and publishing code. Signed-off-by: Giovanni Ravalico <[email protected]>
Adds a new step in the pull request checks workflow that requires changesets. This ensures that no pull request can be merged into the main branch without a corresponding changeset, helping preserve accurate project history. Signed-off-by: Giovanni Ravalico <[email protected]>
This commit introduces a new GitHub Action workflow. This workflow is responsible for code checkout, setup of Node.js with pnpm, dependencies installation, also caching and release automation. Now, every push to the main branch will trigger this release workflow. Signed-off-by: Giovanni Ravalico <[email protected]>
🦋 Changeset detectedLatest commit: 8b500cc The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Three new scripts are added to the scripts section in package.json. They allow using 'changeset' command more conveniently: "changeset:add", "changeset:version", and "changeset:publish". Signed-off-by: Giovanni Ravalico <[email protected]>
Introduced a GitHub Action workflow involved in code checkout, Node.js setup with pnpm, dependencies installation, caching, and release automation. Enhanced PR checks workflow to validate the presence of changesets before merging into main. Also, set up and documented `@changesets/cli` build tool for versioning and publishing code, adding it along with several related packages to the project dependencies. Signed-off-by: Giovanni Ravalico <[email protected]>
This commit updates the changeset status command in the pull request checks workflow. The reference for the changeset status command has been changed from 'main' to 'origin/main'. This makes it more explicit and might address potential issues where the checker failed due to incorrect branch reference. Signed-off-by: Giovanni Ravalico <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is focused on the implementation and subsequent modifications regarding the use of @changesets/cli in our project. This work was carried out through a series of steps, defined by the following commits in chronological order:
feat(pnpm-lock.yaml): Add multiple packages related to '@changesets/cli' The @changesets/cli package was introduced into the project, along with related packages, updating the pnpm-lock.yaml and package.json.
chore(changeset): changeset init Initial setup files and documentation for @changesets/cli were created, helping developers to effectively version and publish their code.
ci(github-workflows): add changesets requirement check to PR workflow A requirement for changesets was added to the pull request workflow, which enforces that no PR can be merged into main without a corresponding changeset.
ci(.github): Add Release workflow A new GitHub Action workflow was introduced which sets up Node.js with pnpm, manages dependencies installation as well as caching and release automation.
chore(package.json): add changeset scripts Three new scripts were added to package.json to enable convenient use of the 'changeset' command.
chore(changeset): Set up changeset cli and CI The @changesets/cli build tool was further configured for versioning and publishing, with added GitHub Action workflows and updated pull request checks.
fix(pull-request-checks-workflow): update changeset status reference The changeset command was updated in the pull-request checks workflow with reference changed from 'main' to 'origin/main'.
Through the implementation of @changesets/cli and the related modifications, we are expecting to handle package versioning more effectively and maintain detailed, autogenerated changelogs. This will contribute to the preservation of precise versioning and release information throughout the project's lifecycle.