release: sync main with development (CI fixes) #66
No reviewers
Labels
No labels
prio_critical
prio_low
type_bug
type_contact
type_issue
type_lead
type_question
type_story
type_task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/hero_collab!66
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Bring main fully in sync with development. The only remaining diff is
.forgejo/workflows/lab-publish.yaml— bringing the auth + RUST_MIN_STACK CI fixes across (24 insertions).Why both branches need the CI fixes
lab-publish.yamltriggers on:Tags (
v0.7.0etc.) are applied to main. Without the fixes, any future tag-triggered publish from main would hit the same auth + rustc SIGSEGV failures we just fixed on dev. CI infrastructure is load-bearing on whatever branch its trigger fires.Brings to main
CARGO_NET_GIT_FETCH_WITH_CLI=true+git config http.extraHeaderfor FORGE_TOKEN auth (hero_planner PR #6 equivalent)RUST_MIN_STACK=16777216at job scope (hero_planner PR #8 equivalent)Merge style
Create merge commit per branching policy.