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: npm/template-oss
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.20.0
Choose a base ref
...
head repository: npm/template-oss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.21.0
Choose a head ref
  • 7 commits
  • 78 files changed
  • 2 contributors

Commits on Nov 27, 2023

  1. feat: release workflow uses composite actions (#380)

    With this overall change, this PR also:
    
    - Allows re-running of release integration step only
    - Makes chores part of the changelog (fixes #378). This also removes the
    ability to force a release PR to be recreated since that was only needed
    to update releases after chores.
    - Creates and uses composite actions for creating check runs and
    installing latest npm
    - Makes publish step always install deps first so they can be used for
    prepare
    - tap@16 + typescript will set appropriate configs (fixes #382)
    - `dist/` dir will be added to `files` array when using `typescript`
    (fixes #383)
    lukekarrys authored Nov 27, 2023
    Configuration menu
    Copy the full SHA
    3d76fc4 View commit details
    Browse the repository at this point in the history

Commits on Nov 28, 2023

  1. Configuration menu
    Copy the full SHA
    9b22b83 View commit details
    Browse the repository at this point in the history
  2. fix: fallback to default release process of 404 from hosted version (#…

    …386)
    
    This also fixes the release manager logging since `core.info` only
    allows a single string argument.
    
    These changes are not tested because they are all tested in #334. But I
    wanted to fix this bug before that gets reviewed.
    lukekarrys authored Nov 28, 2023
    Configuration menu
    Copy the full SHA
    c892260 View commit details
    Browse the repository at this point in the history
  3. feat: use upstream release-please (#334)

    This also adds 100% test coverage to `release-please` and
    `release-manager` using `nock`.
    
    Fixes #177
    lukekarrys authored Nov 28, 2023
    6 Configuration menu
    Copy the full SHA
    2daff23 View commit details
    Browse the repository at this point in the history

Commits on Nov 30, 2023

  1. Configuration menu
    Copy the full SHA
    4fad5d8 View commit details
    Browse the repository at this point in the history

Commits on Dec 1, 2023

  1. fix: pin release-please version (#388)

    - fix: pin release-please version
    
    There is a tradeoff with our usage of release-please. We are using some
    `release-please` classes that we import directly from files like `const
    { ManifestPlugin } = require('release-please/build/src/plugin.js')`. Due
    to how load bearing our release process is for us, I think it is best to
    always pin to an exact version and use dependabot PRs to review all
    `release-please` changes.
    
    - chore: update release please mocks and snapshots
    
    This PR also updates mocks and snapshots. I was not expecting this to
    need to be updated but they failed in #385. It's possible that the mock
    recording or the usage of these mocks inside release-please is
    non-deterministic. I will keep an eye on these tests and refactor in the
    future if they turn out to be flaky.
    lukekarrys authored Dec 1, 2023
    Configuration menu
    Copy the full SHA
    fbe355c View commit details
    Browse the repository at this point in the history
  2. chore: release 4.21.0 (#385)

    🤖 I have created a release *beep* *boop*
    ---
    
    
    ##
    [4.21.0](v4.20.0...v4.21.0)
    (2023-12-01)
    
    ### Features
    
    *
    [`2daff23`](2daff23)
    [#334](#334) use upstream
    release-please (#334) (@lukekarrys)
    *
    [`3d76fc4`](3d76fc4)
    [#380](#380) release workflow
    uses composite actions (#380) (@lukekarrys)
    
    ### Bug Fixes
    
    *
    [`fbe355c`](fbe355c)
    [#388](#388) pin release-please
    version (#388) (@lukekarrys)
    *
    [`4fad5d8`](4fad5d8)
    [#387](#387) make prerelease
    config switch versioning strategy (#387) (@lukekarrys)
    *
    [`c892260`](c892260)
    [#386](#386) fallback to default
    release process of 404 from hosted version (#386) (@lukekarrys)
    *
    [`9b22b83`](9b22b83)
    [#384](#384) give release
    integration workflow correct permissions and secrets (#384)
    (@lukekarrys)
    
    ---
    This PR was generated with [Release
    Please](https://github.com/googleapis/release-please). See
    [documentation](https://github.com/googleapis/release-please#release-please).
    
    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    github-actions[bot] authored Dec 1, 2023
    Configuration menu
    Copy the full SHA
    d13658b View commit details
    Browse the repository at this point in the history
Loading