Skip to content

chore(deps): update dependency happo.io to v13#763

Open
tradeshift-renovate[bot] wants to merge 1 commit intomasterfrom
renovate/happo.io-13.x
Open

chore(deps): update dependency happo.io to v13#763
tradeshift-renovate[bot] wants to merge 1 commit intomasterfrom
renovate/happo.io-13.x

Conversation

@tradeshift-renovate
Copy link
Contributor

This PR contains the following updates:

Package Type Update Change
happo.io devDependencies major ^9.1.6 -> ^13.0.0

Release Notes

happo/happo.io (happo.io)

v13.0.0

Compare Source

This version contains a potentially breaking change for repos that are using Happo via GitHub actions. These changes were originally released as v12.4.1 and v12.4.2, but were reverted in v12.4.3 when they were discovered to be potentially breaking. There are no other changes.

This release fixes an issue where the baseline commit was inconsistently resolved when using Happo in GitHub actions. If you are using a non-zero fetch-depth with the checkout action, this version may result in an error like the following:

Error: Command failed: git merge-base origin/main HEAD
fatal: Not a valid object name origin/main

To update to this version, you will need to make sure that your default branch can be accessed via git in your workflow.

One option is to set fetch-depth: 0 in your checkout action, so that the whole repo is checked out:

- uses: actions/checkout@v4
  with:
    ref: ${{ github.event.pull_request.head.sha || github.ref }}
    fetch-depth: 0

Although this may come with a performance cost, especially for larger repos. Alternatively, you can stick with a non-zero fetch-depth and add a step to fetch your repo's default branch from origin like this:

- uses: actions/checkout@v4
  with:
    ref: ${{ github.event.pull_request.head.sha || github.ref }}
    fetch-depth: 100
- name: Fetch main branch
  if: github.ref != 'refs/heads/main'
  run: git fetch origin main:main

What's Changed

Full Changelog: happo/happo.io@v12.4.2...v13.0.0

v12.4.3

Compare Source

This version reverts all changes from v12.4.1 and v12.4.2, making it identical to v12.4.0. These changes were accidentally breaking and will be published as v13.0.0. If you are already on v12.4.1 or v12.4.2, you should update directly to v13.0.0 and skip this version.

What's Changed

Full Changelog: happo/happo.io@v12.4.2...v12.4.3

v12.4.2

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.4.1...v12.4.2

v12.4.1

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.4.0...v12.4.1

v12.4.0

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.3.0...v12.4.0

v12.3.0

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.2.3...v12.3.0

v12.2.3

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.2.2...v12.2.3

v12.2.2

Compare Source

Full Changelog: happo/happo.io@v12.2.1...v12.2.2

  • Fix deleting old comments (was using the wrong github API rest path)

v12.2.1

Compare Source

Full Changelog: happo/happo.io@v12.2.0...v12.2.1

  • Add verbose logs when posting comment (set VERBOSE=true to enable)

v12.2.0

Compare Source

This minor release adds support for a new HAPPO_GITHUB_TOKEN environment variable, used when posting Happo comments to PRs (this is mainly used in GitHub Enterprise on-premise installations). The new variable takes precedence over HAPPO_GITHUB_USER_CREDENTIALS which is now deprecated. The most simple way to set HAPPO_GITHUB_TOKEN is to use secrets.GITHUB_TOKEN in GitHub actions which is a auth token that is provided automatically to you. E.g.

    env:
      HAPPO_API_KEY: ${{ secrets.HAPPO_API_KEY }}
      HAPPO_API_SECRET: ${{ secrets.HAPPO_API_SECRET }}
      HAPPO_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Related to this is also HAPPO_DELETE_OLD_COMMENTS=true which tells Happo to delete previous status comments so that there's only one remaining. This is useful when you have a PR with a lot of changes made.

    env:
      HAPPO_API_KEY: ${{ secrets.HAPPO_API_KEY }}
      HAPPO_API_SECRET: ${{ secrets.HAPPO_API_SECRET }}
      HAPPO_GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      HAPPO_DELETE_OLD_COMMENTS: true

Full list of changes

Full Changelog: happo/happo.io@v12.1.2...v12.2.0

v12.1.2

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.1.1...v12.1.2

v12.1.1

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.1.0...v12.1.1

v12.1.0

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.0.1...v12.1.0

v12.0.2

Compare Source

What's Changed

This release backports a bugfix from a later version.

Full Changelog: happo/happo.io@v12.0.1...v12.0.2

v12.0.1

Compare Source

What's Changed

Full Changelog: happo/happo.io@v12.0.0...v12.0.1

v12.0.0

Compare Source

What's Changed

Breaking Changes
  • This package only supports Node 18 and later.
  • The makeRequest function removed the deprecated maxTries option. Use retryCount instead.
Other changes

Full Changelog: happo/happo.io@v11.0.1...v12.0.0

v11.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: happo/happo.io@v11.0.0...v11.0.1

v11.0.0

Compare Source

Breaking change

The CI scripts now assume the default branch to be named main. If your default branch is named master, you need to set this environment variable to bring back the old behavior:

BASE_BRANCH=origin/master

Full Changelog: happo/happo.io@v10.1.3...v11.0.0

v10.1.3

Compare Source

What's Changed

Full Changelog: happo/happo.io@v10.1.2...v10.1.3

v10.1.2

Compare Source

What's Changed

Full Changelog: happo/happo.io@v10.1.1...v10.1.2

v10.1.1

Compare Source

What's Changed

Full Changelog: happo/happo.io@v10.1.0...v10.1.1

v10.1.0

Compare Source

What's Changed

Full Changelog: happo/happo.io@v10.0.0...v10.1.0

v10.0.0

Compare Source

What's Changed

Breaking

The jose package uses newer syntax that is not supported on node 14, which makes this a breaking change. If you are using node 16 or newer, you should be good to go!

Other

Full Changelog: happo/happo.io@v9.1.6...v10.0.0


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday in 2125" (UTC).

🚦 Automerge: Enabled.

♻️ Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@tradeshift-renovate tradeshift-renovate bot added dependencies Pull requests that update a dependency file dev labels Jul 1, 2025
@tradeshift-renovate tradeshift-renovate bot requested review from a team as code owners July 1, 2025 01:50
@tradeshift-renovate tradeshift-renovate bot added dependencies Pull requests that update a dependency file dev labels Jul 1, 2025
@ts-sonarqube
Copy link

ts-sonarqube bot commented Jul 1, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file dev

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant