Skip to content
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.

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

chore!: switch to @node-core scope #700

Merged
merged 1 commit into from
Sep 24, 2023
Merged

chore!: switch to @node-core scope #700

merged 1 commit into from
Sep 24, 2023

Conversation

aduh95
Copy link
Contributor

@aduh95 aduh95 commented Jun 1, 2023

Not sure this is ready yet, we may need a new NPM_TOKEN on the repo secret.

Refs: nodejs/TSC#1178

@codecov
Copy link

codecov bot commented Jun 1, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (517a259) 83.03% compared to head (c5f695f) 83.03%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #700   +/-   ##
=======================================
  Coverage   83.03%   83.03%           
=======================================
  Files          37       37           
  Lines        4178     4178           
=======================================
  Hits         3469     3469           
  Misses        709      709           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@MoLow
Copy link
Member

MoLow commented Jun 1, 2023

we should probably also publish one last version to https://www.npmjs.com/package/node-core-utils with a output/warning saying it moved

@aduh95
Copy link
Contributor Author

aduh95 commented Jun 1, 2023

we should probably also publish one last version to https://www.npmjs.com/package/node-core-utils with a output/warning saying it moved

I think we can npm deprecate it without publishing a new version.

@targos
Copy link
Member

targos commented Jun 2, 2023

The current NPM_TOKEN should work. I can replace it with a granular one when the package exists on npm.

MoLow
MoLow previously approved these changes Jun 2, 2023
@MoLow MoLow dismissed their stale review June 2, 2023 12:16

Readme needs an update

@targos
Copy link
Member

targos commented Jun 2, 2023

release-please workflow needs an update as well.

@aduh95 aduh95 merged commit f334713 into main Sep 24, 2023
13 checks passed
@aduh95 aduh95 deleted the scoped-package-name branch September 24, 2023 09:21
nodejs-github-bot pushed a commit to nodejs/node that referenced this pull request Sep 25, 2023
Refs: https://github.com/nodejs/node-core-utils/releases/tag/v4.0.0
PR-URL: #49851
Refs: nodejs/node-core-utils#700
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
ruyadorno pushed a commit to nodejs/node that referenced this pull request Sep 28, 2023
Refs: https://github.com/nodejs/node-core-utils/releases/tag/v4.0.0
PR-URL: #49851
Refs: nodejs/node-core-utils#700
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
ruyadorno pushed a commit to nodejs/node that referenced this pull request Sep 28, 2023
Refs: https://github.com/nodejs/node-core-utils/releases/tag/v4.0.0
PR-URL: #49851
Refs: nodejs/node-core-utils#700
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
alexfernandez pushed a commit to alexfernandez/node that referenced this pull request Nov 1, 2023
Refs: https://github.com/nodejs/node-core-utils/releases/tag/v4.0.0
PR-URL: nodejs#49851
Refs: nodejs/node-core-utils#700
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants