chore(release): monorel.disaresta.com v0.14.0#58
Merged
Conversation
monorel-Release: monorel.disaresta.com v0.14.0 monorel-PreRelease: false
github-actions
Bot
force-pushed
the
monorel/release
branch
from
ec3b9fb to
ec20d29
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by monorel. Merge it to release the following packages:
monorel.disaresta.comReleased changes
monorel.disaresta.com v0.14.0
Minor Changes
monorel now supports Bitbucket Cloud (
provider.name = "bitbucket") alongside GitHub, Gitea / Forgejo, and GitLab. Theinternal/provider/bitbucket/package implements theprovider.Clientinterface against Bitbucket's REST API v2 (hand-rollednet/http; no new direct deps).Auth uses two environment variables:
BITBUCKET_EMAIL(Atlassian account email) andBITBUCKET_TOKEN(Atlassian API token with Bitbucket scopes). The Bitbucket username for git over HTTPS is probed from/2.0/userand cached on the client.Bitbucket Cloud has no first-class Release concept, so
monorel publishis a no-op on Bitbucket; per-packageCHANGELOG.mdis the canonical release-notes source.Plus a defensive recovery mechanism that benefits every provider:
monorel previewnow appends a<!-- monorel-trailers ... -->HTML comment to the PR body.monorel tagfalls back to that block when the merge commit body lacksmonorel-Release:trailers (e.g. because of a squash-merge that rewrote the body). The fallback uses the newprovider.Client.FindPRByMergeCommitmethod, implemented by every provider.See Bitbucket integration.
Fix
cacheseedwriting the wrong h1: hash for released sub-modules(would silently produce broken go.sum entries on every release; see
loglayer/loglayer-go's v2.1.0 incident).Reorder
applyStableso all working-tree mutations happen beforethe seed step, and replace the single-pass seed-and-tidy with
iterate-to-fixpoint to handle cross-sibling dep chains.
Add a
go mod downloadpriming step before offline tidy so freshCI runners (with empty
GOMODCACHE) can resolve third-party deps.The
GOPROXY=offinvariant during tidy is preserved.Document the
actions/setup-goprerequisite (sub-modules withgo 1.25.0directives need a 1.25+ runner sinceGOTOOLCHAIN=localduring tidy blocks auto-download) and the
chore(release):-commitskip filter recipe. See issue #54.
Consumed 2 changeset(s):
bitbucket-provider,cacheseed-fixpoint-and-pipeline-fixes.