Skip to content

catch-up: sync 0.1.1 -> 0.1.4 from Forgejo, keep GitHub git deps - #3

Merged
thedancingdeveloper merged 6 commits into
mainfrom
migration/catch-up-forgejo-0.1.4
Jul 24, 2026
Merged

catch-up: sync 0.1.1 -> 0.1.4 from Forgejo, keep GitHub git deps#3
thedancingdeveloper merged 6 commits into
mainfrom
migration/catch-up-forgejo-0.1.4

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Collaborator

GitHub main was stuck at 0.1.1 while Forgejo main (the ongoing development source) had progressed to 0.1.4 with real changes (BEP-44 crypto/mutable-item-store tests, a rand 0.10 API fix, dependency version bumps). Rebases those Forgejo-exclusive commits onto GitHub main, resolving conflicts by keeping the GitHub git-source deps (not reverting to the Forgejo registry) while taking the version/content bumps. Also fixes the same unused-import warning from a prior clippy-conflict resolution. Verified with cargo check --all-targets, cargo fmt --check, and cargo clippy --all-targets -- -D warnings, all clean.

@AusAgentSmith AusAgentSmith left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed: catches GitHub main up from 0.1.1 to Forgejo's 0.1.4, resolving conflicts to keep GitHub git-source deps while taking Forgejo's real feature/fix commits. CI green.

@thedancingdeveloper
thedancingdeveloper merged commit 05f1aa1 into main Jul 24, 2026
2 checks passed
@thedancingdeveloper
thedancingdeveloper deleted the migration/catch-up-forgejo-0.1.4 branch July 24, 2026 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants