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: yarnpkg/berry
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 52909a5e0d2fe72245957870bcd654218d93ef72
Choose a base ref
...
head repository: yarnpkg/berry
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 6b7621f0736ef7ed423672392882d68592d61c81
Choose a head ref
  • 7 commits
  • 33 files changed
  • 5 contributors

Commits on Jan 30, 2024

  1. Copy the full SHA
    a7a6475 View commit details
  2. Update CHANGELOG.md

    arcanis authored Jan 30, 2024
    Copy the full SHA
    a8db5b1 View commit details
  3. Copy the full SHA
    943a9f0 View commit details

Commits on Feb 14, 2024

  1. docs(plugin-essentials): Improve install command formatting (#6127)

    **What's the problem this PR addresses?**
    <!-- Describe the rationale of your PR. -->
    <!-- Link all issues that it closes. (Closes/Resolves #xxxx.) -->
    
    Improve doc formatting
    
    ...
    
    **How did you fix it?**
    <!-- A detailed description of your implementation. -->
    
    Format it
    
    ...
    
    **Checklist**
    <!--- Don't worry if you miss something, chores are automatically
    tested. -->
    <!--- This checklist exists to help you remember doing the chores when
    you submit a PR. -->
    <!--- Put an `x` in all the boxes that apply. -->
    - [x] I have read the [Contributing
    Guide](https://yarnpkg.com/advanced/contributing).
    
    <!-- See
    https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
    for more details. -->
    <!-- Check with `yarn version check` and fix with `yarn version check
    -i` -->
    - [x] I have set the packages that need to be released for my changes to
    be effective.
    
    <!-- The "Testing chores" workflow validates that your PR follows our
    guidelines. -->
    <!-- If it doesn't pass, click on it to see details as to what your PR
    might be missing. -->
    - [x] I will check that all automated PR checks pass before the PR gets
    reviewed.
    bbodenmiller authored Feb 14, 2024
    Copy the full SHA
    580f593 View commit details

Commits on Mar 4, 2024

  1. fix(compat): update patch for typescript@5.4.1-rc (#6134)

    **What's the problem this PR addresses?**
    
    The PnP compatibility patch for TypeScript doesn't apply to
    `typescript@5.4.1-rc`.
    
    Ref microsoft/TypeScript#35206
    
    **How did you fix it?**
    
    Rebased it.
    
    **Checklist**
    - [x] I have read the [Contributing
    Guide](https://yarnpkg.com/advanced/contributing).
    - [x] I have set the packages that need to be released for my changes to
    be effective.
    - [x] I will check that all automated PR checks pass before the PR gets
    reviewed.
    merceyz authored Mar 4, 2024

    Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
    Copy the full SHA
    aa2eebd View commit details
  2. docs: change i.e. to e.g. in search placeholder (#6142)

    **What's the problem this PR addresses?**
    
    In the website search placeholder text (something like `Search packages
    (i.e. babel, webpack, react, ...)`), the word "i.e." is used
    incorrectly. ["i.e." means "that
    is,"](https://en.wiktionary.org/wiki/i.e.#Usage_notes) but the intended
    meaning here is ["e.g.," meaning "for
    example."](https://en.wiktionary.org/wiki/e.g.)
    
    **How did you fix it?**
    
    Changed the three instances I found of this placeholder text to use
    "e.g." instead.
    
    **Checklist**
    <!--- Don't worry if you miss something, chores are automatically
    tested. -->
    <!--- This checklist exists to help you remember doing the chores when
    you submit a PR. -->
    <!--- Put an `x` in all the boxes that apply. -->
    - [x] I have read the [Contributing
    Guide](https://yarnpkg.com/advanced/contributing).
    
    <!-- See
    https://yarnpkg.com/advanced/contributing#preparing-your-pr-to-be-released
    for more details. -->
    <!-- Check with `yarn version check` and fix with `yarn version check
    -i` -->
    - [x] I have set the packages that need to be released for my changes to
    be effective.
    ~πŸ‘† Not sure how to do that / if it's applicable to docs-only changes.~
    never mind, see
    [comment](#6142 (comment))
    below.
    <!-- The "Testing chores" workflow validates that your PR follows our
    guidelines. -->
    <!-- If it doesn't pass, click on it to see details as to what your PR
    might be missing. -->
    - [x] I will check that all automated PR checks pass before the PR gets
    reviewed.
    pwbriggs authored Mar 4, 2024
    Copy the full SHA
    b880acf View commit details
  3. Releasing 3 new packages

    | Package name | Version |
    | --- | --- |
    | `@yarnpkg/cli` | `4.1.1` |
    | `@yarnpkg/plugin-compat` | `4.0.3` |
    | `@yarnpkg/plugin-essentials` | `4.1.1` |
    yarnbot committed Mar 4, 2024
    Copy the full SHA
    6b7621f View commit details
Loading