Skip to content

chore(deps): reconfigure semantic-release #167

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Sep 2, 2025
Merged

chore(deps): reconfigure semantic-release #167

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
41239ba
chore(deps): reconfigure semantic-release
MikeMcC399 Aug 29, 2025
97cb41a
add semantic-release --dry-run
MikeMcC399 Aug 30, 2025
1505476
update dependencies of semantic-release
MikeMcC399 Aug 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions .github/workflows/main.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,5 +15,12 @@ jobs:
node-version: 22
- run: npm ci
- run: npm test
# - if: github.ref == 'refs/heads/master'
# run: npm run semantic-release
- name: Release to npm registry
# only release from the master branch in parent repository, not in a fork
if: (github.ref == 'refs/heads/master') &&
(github.repository == 'cypress-io/commit-info')
# TODO: remove --dry-run after testing and when a real release is needed
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whenever we are ready for this @MikeMcC399 let me know as I likely need to update the NPM_TOKEN

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AtofStryker

Merge into the master branch is showing that the NPM_TOKEN is indeed missing.

See https://github.com/cypress-io/commit-info/actions/runs/17409432544/job/49422571964

That was the only point that I was unable to view and to test with only having external access privileges.

If cypress-io does not set NPM_TOKEN at an organizational level in GitHub, then it will need to be defined here in this repo, and this should be done now (without any particular urgency), so that the dry-run workflow can be checked as successful.

Thanks once again for reviewing and merging! I will keep doing updates here at a steady pace. They have to come one after another because otherwise it creates package.json conflicts.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikeMcC399 the NPM_TOKEN should now be present and passed on a rerun https://github.com/cypress-io/commit-info/actions/runs/17409432544/job/49430709280

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AtofStryker

Great to see that the dry-run is now working! 🎉 It has revealed that there is a pending patch release due to PRs that were merged back in 2023!

I would currently leave the release workflow in its dry-run setting and come back to this in due course after completing more of the maintenance work.

2.2.1 (v2.2.0...v2.2.1) (2025-09-02)

Bug Fixes

* **deps:** update debug to 4.3.4 🌟 ([e563983](https://github.com/cypress-io/commit-info/commit/e5639832cae219a7150587f987a4fefe5464c2da))
* **deps:** update dependency bluebird to version 3.7.2 🌟 ([#150](https://github.com/cypress-io/commit-info/issues/150)) ([5b96920](https://github.com/cypress-io/commit-info/commit/5b969201e7e7404f022be67315b0089d898906e9))

run: npx semantic-release --dry-run
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
Loading