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: ipfs/aegir
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v39.0.7
Choose a base ref
...
head repository: ipfs/aegir
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v39.0.8
Choose a head ref
  • 2 commits
  • 4 files changed
  • 2 contributors

Commits on May 19, 2023

  1. fix: do not enforce engines in package.json (#1277) 

    The engines field causes warnings on npm but errors on yarn when the
required node version is not met.

Not all of our modules require LTS node and they are used by projects
outside of libp2p/helia/etc.

This change removes the automatic addition of an engines field to a
project's `package.json` while running the `check-project` command,
instead projects that do require a certain node version are free to
define it and deal with the breakage that subsequently occurs.

Partial revert of: #1184
Refs: #1276
    @achingbrain
    achingbrain authored May 19, 2023
    Configuration menu
    Copy the full SHA
    5e9c2fa View commit details
    Browse the repository at this point in the history

  2. chore(release): 39.0.8 [skip ci] 

    ## [39.0.8](v39.0.7...v39.0.8) (2023-05-19)

### Bug Fixes

* do not enforce engines in package.json ([#1277](#1277)) ([5e9c2fa](5e9c2fa)), closes [#1184](#1184)
    @semantic-release-bot
    semantic-release-bot committed May 19, 2023
    Configuration menu
    Copy the full SHA
    fe1e121 View commit details
    Browse the repository at this point in the history
Loading