chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content

chore: release 9.0.0-pre.6 - #5705

Merged
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest
Oct 19, 2022
Merged

chore: release 9.0.0-pre.6#5705
lukekarrys merged 1 commit into
latestfrom
release-please--branches--latest

Conversation

@github-actions

@github-actionsgithub-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
Contributor

🤖 I have created a release beepboop

9.0.0-pre.6

9.0.0-pre.6 (2022-10-19)

⚠️ BREAKING CHANGES

  • npm now outputs some json errors on stdout. Previously npm would output all json formatted errors on stderr, making it difficult to parse as the stderr stream usually has logs already written to it. In the future, npm will differentiate between errors and crashes. Errors, such as E404 and ERESOLVE, will be handled and will continue to be output on stdout. In the case of a crash, npm will log the error as usual but will not attempt to display it as json, even in --json mode. Moving a case from the category of an error to a crash will not be considered a breaking change. For more information see npm/rfcs#482.
  • npm config set will no longer accept deprecated or invalid config options.
  • timing and loglevel changes
    • timing has been removed as a value for --loglevel
    • --timing will show timing information regardless of
      --loglevel, except when --silent
  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • npm will no longer attempt to modify ownership of files it creates
  • this package no longer attempts to change file ownership automatically
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Documentation

Dependencies

arborist: 6.0.0-pre.5

6.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • deprecate boolean install flags in favor of --install-strategy
    • deprecate --global-style, --global now sets --install-strategy=shallow
    • deprecate --legacy-bundling, now sets --install-strategy=nested
  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmaccess: 7.0.0-pre.2

7.0.0-pre.2 (2022-10-19)

Dependencies

libnpmdiff: 5.0.0-pre.3

5.0.0-pre.3 (2022-10-19)

Dependencies

libnpmexec: 5.0.0-pre.5

5.0.0-pre.5 (2022-10-19)

⚠️ BREAKING CHANGES

  • this package no longer attempts to change file ownership automatically

Features

Bug Fixes

Dependencies

libnpmfund: 4.0.0-pre.5

4.0.0-pre.5 (2022-10-19)

Dependencies

libnpmhook: 9.0.0-pre.1

9.0.0-pre.1 (2022-10-19)

Dependencies

libnpmorg: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmpack: 5.0.0-pre.4

5.0.0-pre.4 (2022-10-19)

Dependencies

libnpmpublish: 7.0.0-pre.4

7.0.0-pre.4 (2022-10-19)

Dependencies

libnpmsearch: 6.0.0-pre.1

6.0.0-pre.1 (2022-10-19)

Dependencies

libnpmteam: 5.0.0-pre.1

5.0.0-pre.1 (2022-10-19)

Dependencies

libnpmversion: 4.0.0-pre.1

4.0.0-pre.1 (2022-10-19)

Dependencies


This PR was generated with Release Please. See documentation.

@github-actions

github-actionsBot commented Oct 17, 2022

Copy link
Copy Markdown
ContributorAuthor

Release Manager

Release workflow run: https://github.com/npm/cli/actions/runs/3284538804

Force CI to Rerun for This Release

This PR will be updated and CI will run for every non-chore: commit that is pushed to main. To force CI to rerun, run this command:

gh workflow run release.yml -r latest

Release Checklist for v9.0.0-pre.6

  • 1. Checkout the release branch

    Ensure git status is not dirty on this branch after resetting deps. If it is, then something is probably wrong with the automated release process.

    gh pr checkout 5705 --force
    node . run resetdeps
    node scripts/git-dirty.js
  • 2. Run tests locally

    These have also been running in CI continuously each time the release PR was updated, but it is nice to confirm they pass locally since that is where we will be publishing from.

    node . run lint-all
    node . run test-all
    node scripts/git-dirty.js
  • 3. Check CI status

    gh pr checks --watch
  • 4. Publish workspaces

    Note:
    If we are currently publishing prereleases, make sure to publish with the prerelease tag.

    node . publish -w @npmcli/arborist --tag prerelease
    node . publish -w libnpmaccess --tag prerelease
    node . publish -w libnpmdiff --tag prerelease
    node . publish -w libnpmexec --tag prerelease
    node . publish -w libnpmfund --tag prerelease
    node . publish -w libnpmhook --tag prerelease
    node . publish -w libnpmorg --tag prerelease
    node . publish -w libnpmpack --tag prerelease
    node . publish -w libnpmpublish --tag prerelease
    node . publish -w libnpmsearch --tag prerelease
    node . publish -w libnpmteam --tag prerelease
    node . publish -w libnpmversion --tag prerelease
  • 5. Publish the CLI

    Note:
    This will publish with the dist-tag set to next-9

    make publish
  • 6. Merge release PR

    gh pr merge --rebase
    git checkout latest
    git reset --hard origin/latest
    node . run resetdeps
  • 7. Check For Release Tags

    Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

    gh run watch `gh run list -w release -L 1 --json databaseId -q ".[0].databaseId"`
    
  • 8. Post on Twitter

    New @npmjs release: 9.0.0-pre.6!
    https://github.com/npm/cli/releases/tag/v9.0.0-pre.6
    Release details...
    
  • 9. Trigger docs.npmjs.com update

    Warning:
    The releases.json will need to be updated when a new major release is tagged latest.

    gh workflow run update-cli.yml --repo npm/documentation

@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 4 times, most recently from bb55670 to 0bbc501CompareOctober 18, 2022 07:13
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 22 times, most recently from a2daa13 to ec5c9a6CompareOctober 19, 2022 19:12
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch 2 times, most recently from 17c92ca to e3893fdCompareOctober 19, 2022 19:38
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e3893fd to e72d18dCompareOctober 19, 2022 19:56
@github-actions
github-actionsBotforce-pushed the release-please--branches--latest branch from e72d18d to 728b24bCompareOctober 19, 2022 19:57
@lukekarrys
lukekarrys merged commit 2929899 into latestOct 19, 2022
@lukekarrys
lukekarrys deleted the release-please--branches--latest branch October 19, 2022 20:48
@github-actions

Copy link
Copy Markdown
ContributorAuthor

🤖 Release is at https://github.com/npm/cli/releases/tag/v9.0.0-pre.6 🌻

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

@github-actions

Copy link
Copy Markdown
ContributorAuthor

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

@lukekarrys