biomejs / setup-biome Goto Github PK

Error: Not Found - https://docs.github.com/rest/releases/releases#get-a-release-by-tag-name

https://github.com/biomejs/discord-utils-bot/actions/runs/9246721400/job/25451892086#step:3:1

It worked just a few days ago

This could be a killer feature.

If we were able to install the same version used in the package.json (correct version and architecture), we might be able to install biome binary directly, and we wouldn't need to set up anything else. This is because we don't depend on any runtime.

This could save ton of time in CI times.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update dependency lefthook to v1.6.14

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout digest to a5ac7e5
• chore(deps): update dependency @types/bun to v1.1.3

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

The setup action currently defaults to downloading the latest version of Biome when the version is not specified.

We'd like to explore the possibility of extracting the biome version from the package manager's lock file to setup the same version of Biome as specified in the project's dependencies.

Resolution order

Here's the desired resolution order.

graph LR;
    A[specified version]-->B;
    B[version from lockfile]-->C;
    C[fallback to latest];

Package managers

We'd like to support the following package managers.

• npm (package-lock.json)
• pnpm (package-lock.yaml)
• yarn (yarn.lock)
• bun (bun.lockb)

References

• https://docs.npmjs.com/cli/v10/configuring-npm/package-lock-json#file-format
• https://bun.sh/docs/install/lockfile

The action currently relies on the user configuring Bun to output a human-readable yarn.lock file alongside its native bun.lockb binary file, which requires additional steps.

We'd like to explore the possibility of reading Bun's lockfile to extract the version of Biome, without having to install Bun.

Considering:

..it seems that the semver tagging is somewhat inconsistent. I would assume that all the v2 tags (sans v2.0.1) should point to the same commit (7702017)?

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (semanticCommitTypeAll(chore))

Bun is very fast, and it might speed this action up. It also requires no transpilation or bundling, it can run the ts files directly, so it should also help simplify this repo greatly. If building is still faster (which I doubt), then bun can do that too in a single command. Finally, given that the biome npm package is a thin wrapper over the Rust binary, it's unlikely to break. Because of this, I would suggest looking into this option for better speed :)

(I have not measured anything so I might be wrong!)

Edit: another advantage of this approach is that you'll be able to extract the version from bun's lockfile, since it'll be already installed.

We've started using Renovate in the other repositories, let's replace dependabot with Renovate here too.