Mola #5

Add Node 15 test and plugin references

* prune yarn devDependencies at the end of build * Remove warning message for production flag * Update tests to reflect need of workspace import * install workspace plugin when not present * update fixtures * cache build with yarn 2 * change grep of yarn plugins from yarnrc.yml; delete warning test for production flag * set up buildpack to instead warn that plugin is missing and prompt user to install before build

…cies

Fix tests that depend on packages [changelog skip]

add 10.23.3, 12.20.2 and 14.5.5 to inventory

fix return value for detecting yarn workspace plugin

This change updates the `yarn install` step to use the `--prefer-offline` argument. This avoids reinstalling already-present packages when the local cache has them.

release v184

The Heroku-16 stack reached end-of-life on May 1st, 2021, and from June 1st, 2021, builds will be disabled. This removes support for testing against Heroku-16 in CI. This change is non-breaking as it only affects development (hence why it's landing a few days early), however a changelog entry has been added regardless, for improved visibility into the support status of the stack. Closes GUS-W-9329672.

Drop Heroku-16 from CI test matrix

…ku#921) In production `STACK` is always set to `heroku-{16,18,20}` even for the `-build` stack image variants. This changes make the tests closer to production.

@danielleadams

remove @danielleadams from buildpack README [changelog skip]

add metrics plugin for Node 16

release v185

Refactor $WEB_CONCURRENCY handling

…or and patch levels

Fix broken tests; bump shUnit2 to 2.1.8

Prepare release v186

Fix NODE_BINARY_URL extraction

Upgrade to latest heroku_hatchet (7.3.4)

Corrects tiny typo in conflicting lockfile failure message

Update changelog check to be skippable

…on the project directory

Prefer local packages when present in cache

Add support for running "npm ci" when "npm-shrinkwrap.json" is found on the project directory

Prepare v187 release

Always use local yarn cache with yarn 2

…ages Update node inventory to include previously truncated versions

Prepare release v188

Since it was published the day after the currently listed date: ``` $ h buildpacks:versions heroku/nodejs | head -n3 Version Released At Status ─────── ──────────────────────── ───────── 188 2021-09-10T17:03:08.056Z published ```

Update changelog release date for v188

Revert "Always use local yarn cache with yarn 2"

Prepare release v189

To fix CI on `main`, now that there are newer Yarn versions, which cause `testBuildMetaData` to fail, the same as it did in heroku#934. GUS-W-9981764.

Since by default Dependabot only opens PRs for security fixes, unless an explicit config exists. See: https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates GUS-W-9981100.

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.3.0 to 1.7.0. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.3.0...v1.7.0) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

- Removed unused `parallel_tests` dependency (this repository is using `parallel_split_tests` instead). - Refreshes `Gemfile.lock` to pick up new dependencies. Moving forwards Dependabot will take care of this, but doing so in one go reduces the PR churn to get the repo up to date. Mass-updating is safe since the Ruby deps are only used in CI. GUS-W-9981100.

Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.4 to 2.3.5. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v2.3.4...v2.3.5) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Update node and yarn inventory

Bumps [actions/checkout](https://github.com/actions/checkout) from 2.3.5 to 2.4.0. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v2.3.5...v2.4.0) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>

…ctions/checkout-2.4.0 Bump actions/checkout from 2.3.5 to 2.4.0

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.10.1 to 3.10.2. - [Release notes](https://github.com/rspec/rspec-expectations/releases) - [Changelog](https://github.com/rspec/rspec-expectations/blob/main/Changelog.md) - [Commits](rspec/rspec-expectations@v3.10.1...v3.10.2) --- updated-dependencies: - dependency-name: rspec-expectations dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Update default node version to 16.x

Chore: Update Inventory

…cache

Co-authored-by: Ed Morley <[email protected]>

Document v190 release

…d now

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.10.2 to 3.11.0. - [Release notes](https://github.com/rspec/rspec-expectations/releases) - [Changelog](https://github.com/rspec/rspec-expectations/blob/main/Changelog.md) - [Commits](rspec/rspec-expectations@v3.10.2...v3.11.0) --- updated-dependencies: - dependency-name: rspec-expectations dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Improve support for yarn 2

Prepare v191 release

Replace yarn cache rather than nest it

* Fix additional occurrence of yarn cache nesting * Delete any nested caches * Add changelog note about cache restoration * Fix comment typo

With Yarn 2 there is currently no built in support for pruning `devDependencies`. Instead of removing the cache directory entirely and forcing a new install of just the production dependencies, this PR extracts the `devDependencies` from each `package.json` found in the application and calls `yarn remove` to prune them.

…_pruning Prune devDependencies for Yarn 2

Noticed this was causing CI failures after merging heroku#990. This should get the failing tests sorted.

Added inventory entry for yarn 1.22.18

…lease Merged changelog entries before publishing buildpack

There is an issue with the changes to prune the yarn 2 cache that, in certain situations, would cause all devDependencies to be reinstalled during the prune stage which is the opposite result of the intended fix. This can cause slug sizes to increase for customers so this PR restores the previous cache clearing behavior.

…_pruning Revert changes introduced in heroku#990

For debugging or for folks who are curious about how the buildpack works. Similar implementation here: heroku/heroku-buildpack-python#226

Bumps [actions/checkout](https://github.com/actions/checkout) from 2.4.0 to 3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v2.4.0...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.0 to 1.7.1. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.7.0...v1.7.1) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

feat: set xtrace if $BUILDPACK_XTRACE set

Fixing up the changelog after merging heroku#925

Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: naveensrinivasan <[email protected]>

When a new version of npm is installed only the specified compatible version is logged, not the resolved/installed one. This differs from when installing node, where both versions are logged. Logging the exact version helps in debugging and adds clarity. Before: ```sh Resolving node version ~16... Downloading and installing node 16.14.2... Bootstrapping npm ~8 (replacing 8.5.0)... npm ~8 installed ``` After: ```sh Resolving node version ~16... Downloading and installing node 16.14.2... Bootstrapping npm ~8 (replacing 8.5.0)... npm 8.6.0 installed ``` Co-authored-by: Josh W Lewis <[email protected]>

Adds a custom Yarn 2 plugin to handle `devDependency` pruning.

…_pruning_attempt_2 Prune devDependencies for Yarn 2

After monitoring the custom Yarn 2 plugin for a period of time there doesn't seem to be any issues from the 20% of builds that it has been active on. This PR enables this feature completely and removes the old code path that used to handle pruning for Yarn 2.

…pruning Enable devDependency pruning for Yarn 2

The Node.js binaries are not stack-specific, so no buildpack/binary changes are needed for Heroku-22 - only testing it in CI. GUS-W-10343867.

* Metrics support for Node 17, 18 (not 12) * Update test version range to include Node.js 17 and 18 * Update metrics plugins * Add a node 16 spec * Add a node-17 spec * Tie down range-with-space version range, so it'll work with heroku-18+Node18 * Add a spec for Node 18.x * Add failure message for heroku-18 and Node.js 18 * Add a spec for heroku-18/Node 18 incompatibilty * Use PCRE regex on failure check * Adjust regex * Add log grep debugging * Actually grep the file * Make sure npm --version errors make it to the log * Redirect more stderr so that errors end up in logs * Capture npm --version stderr in the output logs * Add additional debugging * Add additional debugging * More debug logs =( * Still debugging * Fix npm --version redirection * Clean up debugging and add comments * Add node-16-metrics test * add node-17-metrics test * Add node-18-metrics test * Update changelog for Node 17 and 18 support * Adjust test-range-with-space expectation * Update CHANGELOG.md Co-authored-by: Ed Morley <[email protected]> * Update lib/failure.sh Co-authored-by: Ed Morley <[email protected]> * Update lib/binaries.sh Co-authored-by: Ed Morley <[email protected]> * Update lib/binaries.sh Co-authored-by: Ed Morley <[email protected]> * Update lib/binaries.sh Co-authored-by: Ed Morley <[email protected]> * Update spec/ci/node_16_metrics_spec.rb Co-authored-by: Ed Morley <[email protected]> Co-authored-by: Ed Morley <[email protected]>

Update CHANGELOG.md before publishing v196

* Drop yarn-native-cache feature * Drop fixture feature setting * Drop yarn-native-cache feature * Update test expectations: it was testing an impossible scenario * Add changelog entry for feature flag removal

The [Node support docs](https://devcenter.heroku.com/articles/nodejs-support#skip-pruning) state that Yarn dependency pruning can be skipped by setting `YARN_PRODUCTION=false` but this only works with Yarn v1 since using the `YARN_PRODUCTION` environment variable with Yarn v2+ will cause `yarn` commands to fail. This PR will: * detect when Yarn v2+ is used in the build and raise an actionable error if the `YARN_PRODUCTION` is set * checks for the presence of a `YARN2_SKIP_PRUNING` environment variable to determine if we should skip pruning or not

Since `npm ci` removes any existing `node_modules` folder before installing, to get proper caching behavior we need to cache the npm cache instead.

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.1 to 1.7.2. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.7.1...v1.7.2) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

S3 URLs where the bucket name is part of the URL path are deprecated. Instead, it's recommended to use the virtual-hosted style references, where the bucket name is part of the domain. The latter allows AWS to use DNS to direct requests directly to the appropriate region's S3 endpoint, rather than having to route via the global S3 endpoint (which AWS describe as being a single point of failure/harder to scale etc). There is a small chance this may also help with some of the S3 reliability issues seen in `heroku/builder` Circle CI runs - however even if it doesn't, at least we'll no longer be using the deprecated URLs/endpoints. The `lib/vendor/resolve-*` binaries were regenerated using `make build-production`. See: https://aws.amazon.com/blogs/aws/amazon-s3-path-deprecation-plan-the-rest-of-the-story/ https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html https://docs.aws.amazon.com/general/latest/gr/s3.html#s3_region GUS-W-11283397.

Since `jq` now exists on all stacks: https://devcenter.heroku.com/articles/stack-packages Removing since this means one fewer `curl` call to which retries etc have to be added shortly.

In the shimmed CNBs used in `heroku/builder` we have been seeing quite a few transient errors related to buildpacks downloading from S3. Adding appropriate retries and connection timeouts to all of our buildpack's curl usages should help with these, as well as make builds more reliable in general for users on Heroku, plus also anyone using a shimmed CNB locally with Pack CLI (where the network connection may be even less reliable). The `--retry-connrefused` option has been used since otherwise curl doesn't retry cases where the connection was refused. Ideally we would use `--retry-all-errors` which takes that one step further, however that option was only added in curl 7.71, so is only supported by Heroku-22+. For more on curl options, see: https://curl.se/docs/manpage.html GUS-W-11283397.

To pick up heroku#1013, heroku#1016 & heroku#1017. GUS-W-11283397.

…es (heroku#1022) Bumps [got](https://github.com/sindresorhus/got) from 11.8.3 to 11.8.5. - [Release notes](https://github.com/sindresorhus/got/releases) - [Commits](sindresorhus/got@v11.8.3...v11.8.5) --- updated-dependencies: - dependency-name: got dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Update Node.js inventory * Update yarn inventory

* Support GitHub Actions in etc/hatchet.sh * Drop debugging line * Support CI setup on GitHub Actions

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.11.0 to 3.11.1. - [Release notes](https://github.com/rspec/rspec-expectations/releases) - [Changelog](https://github.com/rspec/rspec-expectations/blob/main/Changelog.md) - [Commits](rspec/rspec-expectations@v3.11.0...v3.11.1) --- updated-dependencies: - dependency-name: rspec-expectations dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Since: - The app is deprecated and due to be switched off shortly. - The buildpack should have as few dependencies on external resources as possible (particularly those not productionised or behind CDN). - We especially should not have dependencies on `herokuapp.com` domains, given the reduced flexibility and risk of subdomain takeover. Fixes heroku#1015. GUS-W-11843580.

GUS-W-11843580.

* Add workflow heroku/heroku-buildpack-nodejs/buildpack-tests * Matrixify unit-test * Correct push arguments * Rename CI workflow * Matrixify unit build tests * Use secrets for hatchet API key * Don't try to detect CI branch name * GitHub Actions workflow improvements * Use GITHUB_HEAD_REF if present * Add debugging for flaky tests * Disable colors for yarn prune tests * Drop debugging lines * Drop container for heroku-build tests * Add STACK to heroku-build tests * Add timeout-minutes to cancelled job * Add tearDown function to prevent running out of disk during CI * Run in heroku:{STACK}-build again * Use setup-ruby for caching * Drop circle config * Fix error constant * Run hatchet tests in expensive mode to bypass free dyno hour quotas * Enable hatchet run_multi too * Drop HATCHET_RUN_MULTI Co-authored-by: Josh W Lewis <[email protected]>

* feat: Yarn 4 support for dependency pruning Co-authored-by: Reece Dunham <[email protected]>

To reduce the churn + email notification noise slightly. GitHub will still open PRs for any security issues outside of the monthly cadence.

This PR also addresses the following dependabot security alerts: - https://github.com/heroku/heroku-buildpack-nodejs/security/dependabot/11 - https://github.com/heroku/heroku-buildpack-nodejs/security/dependabot/4 - https://github.com/heroku/heroku-buildpack-nodejs/security/dependabot/12

* Change the default Node.js to 18.x * Add changelog entry for default version change * Update CHANGELOG.md Co-authored-by: Ed Morley <[email protected]> * Fallback to Node.js 16.x default on heroku-18 * Update changelog entry for heroku-18 exception Co-authored-by: Ed Morley <[email protected]>

* Update metrics plugins for 19.x support * Enable 19.x and drop 17.x for vX specs * Add node 19 hatchet tests * Add changelog entry for Node.js 19.x support

* Update to go 1.19 and recompile * Add changelog entry for go update

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.7.2 to 1.8.1. - [Release notes](https://github.com/stretchr/testify/releases) - [Commits](stretchr/testify@v1.7.2...v1.8.1) --- updated-dependencies: - dependency-name: github.com/stretchr/testify dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.11.1 to 3.12.0. - [Release notes](https://github.com/rspec/rspec-expectations/releases) - [Changelog](https://github.com/rspec/rspec-expectations/blob/main/Changelog.md) - [Commits](rspec/rspec-expectations@v3.11.1...v3.12.0) --- updated-dependencies: - dependency-name: rspec-expectations dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Allow engines.yarn to be specified for yarn berry * Update changelog with yarn berry channges * Bump the version in CHANGELOG * Update test for yarn 2 project specifying engine * Don't use yarn 2 in tests; it's not available yet

Bumps [heroku_hatchet](https://github.com/heroku/hatchet) from 7.3.4 to 8.0.1. - [Release notes](https://github.com/heroku/hatchet/releases) - [Changelog](https://github.com/heroku/hatchet/blob/main/CHANGELOG.md) - [Commits](heroku/hatchet@v7.3.4...v8.0.1) --- updated-dependencies: - dependency-name: heroku_hatchet dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

As of Hatchet v8.x, Hatchet now: - Removes the apps it creates after each test runs, rather than only enabling maintenance mode. This occurs even if an individual test fails. - Cleans up older apps iff it runs into the app limit. (This is only done when the app limit is hit, in order to prevent hundreds of unnecessary API requests, when test concurrency is high.) However, leftover apps can still occur in the following cases: - The GitHub Actions run is cancelled, or aborts in a non-clean way. - If a Hatchet bug (or a mis-use of Hatchet by the tests) cause Hatchet to exit non-cleanly. - If there is a platform incident causing the Heroku API to not be available. Therefore, this scheduled cleanup job has been added to catch any such leftover apps. It runs daily at 6am UTC, and can also be triggered manually via the GitHub dashboard. The cleanup job only deletes apps older than 10 minutes, so that it doesn't break any in progress CI jobs. GUS-W-12629391.

) * Use version resolver from heroku/nodejs CNB The heroku/nodejs CNB uses a version resolver that is written in rust and leverages a local inventory to resolve both Node.js and Yarn version ranges to an available version. This will replace the Go version which relied on querying the contents of an S3 bucket. This change should reduce the dependency on http during builds. It also unifies the heroku/nodejs CNB and v2 buildpacks to use the same version resolution system. * Don't unit test the go binaryin CI; it's been deleted * Rework resolve function to behave correctly * Report version resolution only for v2 * Read error message from stderr too * Add changelog for version resolver change * Add makefile targets for building rust resolvers * Add changelog entry for release

…es (heroku#1055) Bumps [json5](https://github.com/json5/json5) from 2.2.1 to 2.2.3. - [Release notes](https://github.com/json5/json5/releases) - [Changelog](https://github.com/json5/json5/blob/main/CHANGELOG.md) - [Commits](json5/json5@v2.2.1...v2.2.3) --- updated-dependencies: - dependency-name: json5 dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…eroku#1059) Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1. - [Release notes](https://github.com/kornelski/http-cache-semantics/releases) - [Commits](kornelski/http-cache-semantics@v4.1.0...v4.1.1) --- updated-dependencies: - dependency-name: http-cache-semantics dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [rspec-expectations](https://github.com/rspec/rspec-expectations) from 3.12.0 to 3.12.2. - [Release notes](https://github.com/rspec/rspec-expectations/releases) - [Changelog](https://github.com/rspec/rspec-expectations/blob/main/Changelog.md) - [Commits](rspec/rspec-expectations@v3.12.0...v3.12.2) --- updated-dependencies: - dependency-name: rspec-expectations dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Use cargo install instead of cloning the repo manually * Add newlines instead of ;

[W-12665751](https://gus.lightning.force.com/a07EE00001Mrns7YAB)

- includes fixed node inventory for 18.15.0

* Add inventory update automation * Use rust binaries that are hopefully on the PATH * Don't run inventory updates on push * Simplify binary installation to 1 line, add action versions

Added yarn version 3.5.0. Co-authored-by: joshwlewis <[email protected]>

Added node version 19.8.1, 19.8.0. Co-authored-by: joshwlewis <[email protected]>

…e changelog (heroku#1077)

Added yarn version 4.0.0-rc.42, 4.0.0-rc.41. Co-authored-by: joshwlewis <[email protected]>

Added node version 16.20.0. Co-authored-by: joshwlewis <[email protected]>

Bumps [heroku_hatchet](https://github.com/heroku/hatchet) from 8.0.1 to 8.0.2. - [Release notes](https://github.com/heroku/hatchet/releases) - [Changelog](https://github.com/heroku/hatchet/blob/main/CHANGELOG.md) - [Commits](heroku/hatchet@v8.0.1...v8.0.2) --- updated-dependencies: - dependency-name: heroku_hatchet dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Added node version 19.9.0. Co-authored-by: joshwlewis <[email protected]>

Added node version 18.16.0. Co-authored-by: joshwlewis <[email protected]>

* Prepare v209 release * What year is it? Co-authored-by: Richard Schneeman <[email protected]> --------- Co-authored-by: Richard Schneeman <[email protected]>

Added node version 20.0.0. Co-authored-by: joshwlewis <[email protected]>

[W-13067215](https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00001PpQHxYAN/view)

* Updates metrics plugins and tests for Node 20 [W-13067131](https://gus.lightning.force.com/lightning/r/ADM_Work__c/a07EE00001Pp1ZpYAJ/view)

* Drop all handling for heroku-18 * Changelog entry for heroku-18 EOL

Added yarn version 4.0.0-rc.43, 3.5.1. Co-authored-by: joshwlewis <[email protected]>

Added node version 20.1.0. Co-authored-by: joshwlewis <[email protected]>

Added yarn version 4.0.0-rc.44. Co-authored-by: joshwlewis <[email protected]>

Added node version 20.2.0. Co-authored-by: joshwlewis <[email protected]>

Pull in latest changes

Commits on Jun 30, 2021

fix double local var def in bound_memory

dzuelke committed Jun 30, 2021

Configuration menu

View commit details

Copy full SHA for 8770f1b

Browse repository at this point

Copy the full SHA

8770f1b View commit details

Browse the repository at this point in the history

Commits on May 19, 2022

Update CHANGELOG.md

colincasey authored May 19, 2022

Configuration menu

View commit details

Copy full SHA for 3b6a939

Browse repository at this point

Copy the full SHA

3b6a939 View commit details

Browse the repository at this point in the history

Commits on May 24, 2023

Prepare v213 release (heroku#1098 )

joshwlewis authored May 24, 2023

Configuration menu

View commit details

Copy full SHA for 4ae446b

Browse repository at this point

Copy the full SHA

4ae446b View commit details

Browse the repository at this point in the history

Mola #5

Are you sure you want to change the base?

Mola #5

Commits on Feb 1, 2021

Commits on Feb 2, 2021

Commits on Feb 3, 2021

Commits on Feb 9, 2021

Commits on Feb 10, 2021

Commits on Feb 11, 2021

Commits on Feb 26, 2021

Commits on Apr 28, 2021

Commits on May 20, 2021

Commits on May 27, 2021

Commits on Jun 1, 2021

Commits on Jun 2, 2021

Commits on Jun 3, 2021

Commits on Jun 30, 2021

Commits on Jul 1, 2021

Commits on Aug 9, 2021

Commits on Aug 10, 2021

Commits on Aug 11, 2021

Commits on Aug 12, 2021

Commits on Aug 31, 2021

Commits on Sep 1, 2021

Commits on Sep 2, 2021

Commits on Sep 4, 2021

Commits on Sep 8, 2021

Commits on Sep 9, 2021

Commits on Sep 13, 2021

Commits on Sep 14, 2021

Commits on Oct 4, 2021

Commits on Oct 17, 2021

Commits on Dec 14, 2021

Commits on Jan 14, 2022

Commits on Jan 28, 2022

Commits on Jan 31, 2022

Commits on Feb 1, 2022

Commits on Feb 2, 2022

Commits on Feb 3, 2022

Commits on Feb 4, 2022

Commits on Feb 7, 2022

Commits on Feb 10, 2022

Commits on Feb 14, 2022

Commits on Feb 16, 2022

Commits on Mar 15, 2022

Commits on Mar 23, 2022

Commits on Mar 28, 2022

Commits on Mar 30, 2022

Commits on Apr 1, 2022

Commits on Apr 4, 2022

Commits on Apr 5, 2022

Commits on Apr 11, 2022

Commits on Apr 12, 2022

Commits on Apr 13, 2022

Commits on May 18, 2022

Commits on May 19, 2022

Commits on May 26, 2022

Commits on May 31, 2022

Commits on Jun 1, 2022

Commits on Jun 3, 2022

Commits on Jun 7, 2022

Commits on Jun 9, 2022

Commits on Jun 13, 2022

Commits on Jun 15, 2022

Commits on Sep 6, 2022

Commits on Sep 26, 2022

Commits on Sep 29, 2022

Commits on Oct 3, 2022

Commits on Oct 11, 2022

Commits on Oct 18, 2022

Commits on Oct 19, 2022

Commits on Nov 3, 2022

Commits on Nov 10, 2022

Commits on Feb 10, 2023

Commits on Mar 2, 2023

Commits on Mar 3, 2023

Commits on Mar 9, 2023

Commits on Mar 13, 2023

Commits on Mar 21, 2023

Commits on Mar 22, 2023