Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: netlify/cli
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v19.1.0
Choose a base ref
...
head repository: netlify/cli
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v19.1.1
Choose a head ref
  • 4 commits
  • 9 files changed
  • 3 contributors

Commits on Mar 26, 2025

  1. test(e2e): isolate E2E tests and remove destructive actions

    The E2E suite has a litany of problems, including that it is fairly
    complex, doesn't work very well locally and destructively modifies the
    workspace, and doesn't isolate tests from each other particularly well.
    The tests rely on wrapper scripts to work properly, which makes it
    unnecessarily difficult to run E2E tests.
    
    This changeset makes a few changes to the E2E test to help address these
    issues The tl;dr is that tests are now self contained without any need
    for wrapper scripts and are better isolated. Other notable changes
    include:
    
    - Each test now gets its own isolated Verdaccio registry; the Verdaccio
      registry storage is no longer shared between tests and is no longer
      persisted between test invocations.
    - The CLI is now published to the (isolated) Verdaccio registry from a
      temporary workspace, which is a copy of the project workspace. We no
      longer publish to Verdaccio from the project workspace. This ensures
      that destructive actions that occur on publish don't alter the
      workspace, and ensures that one test can't modify the registry in a
      way that impacts another test.
    - The tests no longer rely on wrapper scripts (which ran `vitest` in a
      subprocess and didn't always work locally (depending on your `PATH`).
    - I also converted the tests to TypeScript while I was at it.
    
    Theoretically, these changes mean we can run E2E tests concurrently,
    though I haven't done that in this changeset. We could also now merge
    the E2E vitest configuration into the primary Vitest config (though I
    haven't done that here, either).
    ndhoule committed Mar 26, 2025
    Copy the full SHA
    271b518 View commit details
  2. test(e2e): always test against npm+pnpm+yarn

    ndhoule committed Mar 26, 2025
    1

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    Copy the full SHA
    c4b9e4d View commit details

Commits on Mar 27, 2025

  1. fix: temporarily remove broken postinstal hook (#7142)

    See #7141.
    
    This will be faster than reverting a bunch of stacked PRs, and it's been too long to unpublish from the NPM registry.
    serhalp authored Mar 27, 2025
    1

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    Copy the full SHA
    7319da2 View commit details
  2. chore(main): release 19.1.1 (#7143)

    Co-authored-by: token-generator-app[bot] <82042599+token-generator-app[bot]@users.noreply.github.com>
    token-generator-app[bot] authored Mar 27, 2025
    1
    Copy the full SHA
    957e9ba View commit details
Loading