The prerelases published on each PR merge don't match the future version

JAForbes / pr-release

Manage releases with pull request descriptions and metadata instead of config.

6 stars 1 forks source link

Closed pygy closed 2 years ago

pygy commented 2 years ago

In Mithril, the release PR has already beeen bumped to v3.0.0.

However, the prereleases over at npm are based off v2.2.3. This seems wrong...

JAForbes commented 2 years ago

Yeah interesting, I'll take a look

JAForbes commented 2 years ago

An oversight on my part, mithril having a default branch of master (instead of main) requires --target to be explicitly set.

pygy commented 2 years ago

Yes, thanks for the fix :-)

This makes me think we could easliy rename that branch to main.