Skip to content

build(deps): bump github.com/danmestas/go-libfossil in / - #204

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go_modules-cd07540e7f
Open

build(deps): bump github.com/danmestas/go-libfossil in /#204
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/go_modules-cd07540e7f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 16, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/danmestas/go-libfossil in / from 0.11.1 to 0.12.0.

Updates github.com/danmestas/go-libfossil from 0.11.1 to 0.12.0

Release notes

Sourced from github.com/danmestas/go-libfossil's releases.

v0.12.0

What's Changed

... (truncated)

Changelog

Sourced from github.com/danmestas/go-libfossil's changelog.

[0.12.0] - 2026-10-13

Added

  • CloneOpts.PullPhantoms makes Clone fetch the artifacts its clone rounds left missing with a follow-up pull session, and fail if any are still missing after it, as every clone did before. That pull departs from sync-protocol-01 Section 8.2, which sends no clone, pull or push card after clone_seqno 0, so it is off by default (tracked in #424).
  • Repo.SetHashPolicy sets the hash policy by its name, as fossil hash-policy NEW-POLICY does: sha1, auto, sha3, sha3-only or shun-sha1, matched case-sensitively and exactly (artifact-format-01 7.1). Any other string, a wrong-case or empty one included, is an error that leaves the policy unchanged. Asking for auto in a repository that already holds a SHA3-named artifact stores sha3 (7.3), as fossil does. New conformance cases drive each name, wrong-case names, unknown names and the empty name through it, so AF-7.1-2 is now covered rather than partial.
  • Checkout.ResolveVersion resolves a version name the way Repo.ResolveVersion does and also resolves the names relative to the checkout: current, prev/previous (its primary parent) and next (a child, primary first, then the newest), as fossil does inside a checkout (repo-state-01 §8.3). A keyword that names nothing, such as prev at a root, falls through to the other forms. ckout stays an ordinary name: it is a keyword only in the checkout-inclusive request, Checkout.ResolveWorking. Repo.ResolveVersion is unchanged. A checkout with no recorded version has no relative names, and every other form still resolves. The merge command resolves its version through the checkout, so merge prev and merge next work.
  • Checkout.ResolveWorking is fossil's checkout-inclusive request (ci+, repo-state-01 §8.3) and returns a WorkingVersion. While the checkout has a version, ckout names the working files: Working is set and RID is the checkout's version. No pseudo-RID is exported. Every other name, and ckout in a checkout with no version, resolves as Checkout.ResolveVersion does, except that only check-ins can answer: the request is a check-in request, so a technote carrying the tag does not. ckout is a keyword only as the whole name, so ckout. and root:ckout read it as an ordinary name. ckout is a keyword only in ci+ (as the 2026-10-13 erratum has it, and fossil), so ResolveVersion and ResolveBranchStart read it as an ordinary name. New repostate.8.3 cases run the request against fossil test-name-to-id --type ci+: ckout over a tag of that name, with and without a checkout version, and ckout as the tag under the untyped request (RS-8.3-4; tracked in #419).
  • Repo.ResolveBranchStart is fossil's branch-type request: it resolves a name, then returns the first check-in of the branch the result is on (repo-state-01 §8.3). It follows the draft where fossil 2.28 differs: fossil walks back only from a tag:NAME or plain-name result, so a hash, tip or a date gives the named check-in itself there. As the draft and fossil both require, only check-ins can match, so a technote tagged with the branch name does not shadow the branch.

... (truncated)

Commits
  • 9efb84a chore(release): v0.12.0 changelog (#435)
  • 0e7551a fix(manifest): maintain the leaf table incrementally (RS-7.3-3) (#434)
  • fb63e4b test(conformance): refresh the corrected sync §9.4 erratum (#431)
  • a7fa8c8 test(conformance): re-pin the -01 drafts with the 2026-10-13 errata (#430)
  • 72a5e78 chore: ignore .agent-config at any depth; drop a stray tool trace (#429)
  • 088e9fd feat(sync): add share-links mode for pragma req-links and link (#428)
  • e430eaf fix(sync): answer a client clone_seqno with bad command; make Clone's phantom...
  • 201619b test(conformance): report deviations marked on repo-state API cases (#423)
  • 06d3506 fix(sync): run each request, reply and clone round in one transaction (#422)
  • 07fc13e feat(resolve): checkout-inclusive request where ckout names the working files...
  • Additional commits viewable in compare view

Updates github.com/danmestas/go-libfossil from 0.11.1 to 0.12.0

Release notes

Sourced from github.com/danmestas/go-libfossil's releases.

v0.12.0

What's Changed

... (truncated)

Changelog

Sourced from github.com/danmestas/go-libfossil's changelog.

[0.12.0] - 2026-10-13

Added

  • CloneOpts.PullPhantoms makes Clone fetch the artifacts its clone rounds left missing with a follow-up pull session, and fail if any are still missing after it, as every clone did before. That pull departs from sync-protocol-01 Section 8.2, which sends no clone, pull or push card after clone_seqno 0, so it is off by default (tracked in #424).
  • Repo.SetHashPolicy sets the hash policy by its name, as fossil hash-policy NEW-POLICY does: sha1, auto, sha3, sha3-only or shun-sha1, matched case-sensitively and exactly (artifact-format-01 7.1). Any other string, a wrong-case or empty one included, is an error that leaves the policy unchanged. Asking for auto in a repository that already holds a SHA3-named artifact stores sha3 (7.3), as fossil does. New conformance cases drive each name, wrong-case names, unknown names and the empty name through it, so AF-7.1-2 is now covered rather than partial.
  • Checkout.ResolveVersion resolves a version name the way Repo.ResolveVersion does and also resolves the names relative to the checkout: current, prev/previous (its primary parent) and next (a child, primary first, then the newest), as fossil does inside a checkout (repo-state-01 §8.3). A keyword that names nothing, such as prev at a root, falls through to the other forms. ckout stays an ordinary name: it is a keyword only in the checkout-inclusive request, Checkout.ResolveWorking. Repo.ResolveVersion is unchanged. A checkout with no recorded version has no relative names, and every other form still resolves. The merge command resolves its version through the checkout, so merge prev and merge next work.
  • Checkout.ResolveWorking is fossil's checkout-inclusive request (ci+, repo-state-01 §8.3) and returns a WorkingVersion. While the checkout has a version, ckout names the working files: Working is set and RID is the checkout's version. No pseudo-RID is exported. Every other name, and ckout in a checkout with no version, resolves as Checkout.ResolveVersion does, except that only check-ins can answer: the request is a check-in request, so a technote carrying the tag does not. ckout is a keyword only as the whole name, so ckout. and root:ckout read it as an ordinary name. ckout is a keyword only in ci+ (as the 2026-10-13 erratum has it, and fossil), so ResolveVersion and ResolveBranchStart read it as an ordinary name. New repostate.8.3 cases run the request against fossil test-name-to-id --type ci+: ckout over a tag of that name, with and without a checkout version, and ckout as the tag under the untyped request (RS-8.3-4; tracked in #419).
  • Repo.ResolveBranchStart is fossil's branch-type request: it resolves a name, then returns the first check-in of the branch the result is on (repo-state-01 §8.3). It follows the draft where fossil 2.28 differs: fossil walks back only from a tag:NAME or plain-name result, so a hash, tip or a date gives the named check-in itself there. As the draft and fossil both require, only check-ins can match, so a technote tagged with the branch name does not shadow the branch.

... (truncated)

Commits
  • 9efb84a chore(release): v0.12.0 changelog (#435)
  • 0e7551a fix(manifest): maintain the leaf table incrementally (RS-7.3-3) (#434)
  • fb63e4b test(conformance): refresh the corrected sync §9.4 erratum (#431)
  • a7fa8c8 test(conformance): re-pin the -01 drafts with the 2026-10-13 errata (#430)
  • 72a5e78 chore: ignore .agent-config at any depth; drop a stray tool trace (#429)
  • 088e9fd feat(sync): add share-links mode for pragma req-links and link (#428)
  • e430eaf fix(sync): answer a client clone_seqno with bad command; make Clone's phantom...
  • 201619b test(conformance): report deviations marked on repo-state API cases (#423)
  • 06d3506 fix(sync): run each request, reply and clone round in one transaction (#422)
  • 07fc13e feat(resolve): checkout-inclusive request where ckout names the working files...
  • Additional commits viewable in compare view

Updates github.com/danmestas/go-libfossil from 0.11.1 to 0.12.0

Release notes

Sourced from github.com/danmestas/go-libfossil's releases.

v0.12.0

What's Changed

... (truncated)

Changelog

Sourced from github.com/danmestas/go-libfossil's changelog.

[0.12.0] - 2026-10-13

Added

  • CloneOpts.PullPhantoms makes Clone fetch the artifacts its clone rounds left missing with a follow-up pull session, and fail if any are still missing after it, as every clone did before. That pull departs from sync-protocol-01 Section 8.2, which sends no clone, pull or push card after clone_seqno 0, so it is off by default (tracked in #424).
  • Repo.SetHashPolicy sets the hash policy by its name, as fossil hash-policy NEW-POLICY does: sha1, auto, sha3, sha3-only or shun-sha1, matched case-sensitively and exactly (artifact-format-01 7.1). Any other string, a wrong-case or empty one included, is an error that leaves the policy unchanged. Asking for auto in a repository that already holds a SHA3-named artifact stores sha3 (7.3), as fossil does. New conformance cases drive each name, wrong-case names, unknown names and the empty name through it, so AF-7.1-2 is now covered rather than partial.
  • Checkout.ResolveVersion resolves a version name the way Repo.ResolveVersion does and also resolves the names relative to the checkout: current, prev/previous (its primary parent) and next (a child, primary first, then the newest), as fossil does inside a checkout (repo-state-01 §8.3). A keyword that names nothing, such as prev at a root, falls through to the other forms. ckout stays an ordinary name: it is a keyword only in the checkout-inclusive request, Checkout.ResolveWorking. Repo.ResolveVersion is unchanged. A checkout with no recorded version has no relative names, and every other form still resolves. The merge command resolves its version through the checkout, so merge prev and merge next work.
  • Checkout.ResolveWorking is fossil's checkout-inclusive request (ci+, repo-state-01 §8.3) and returns a WorkingVersion. While the checkout has a version, ckout names the working files: Working is set and RID is the checkout'...

    Description has been truncated

@dependabot
build(deps): bump github.com/danmestas/go-libfossil in /
567f524 
Bumps [github.com/danmestas/go-libfossil](https://github.com/danmestas/go-libfossil) in `/` from 0.11.1 to 0.12.0.


Updates `github.com/danmestas/go-libfossil` from 0.11.1 to 0.12.0
- [Release notes](https://github.com/danmestas/go-libfossil/releases)
- [Changelog](https://github.com/danmestas/go-libfossil/blob/main/CHANGELOG.md)
- [Commits](danmestas/go-libfossil@v0.11.1...v0.12.0)

Updates `github.com/danmestas/go-libfossil` from 0.11.1 to 0.12.0
- [Release notes](https://github.com/danmestas/go-libfossil/releases)
- [Changelog](https://github.com/danmestas/go-libfossil/blob/main/CHANGELOG.md)
- [Commits](danmestas/go-libfossil@v0.11.1...v0.12.0)

Updates `github.com/danmestas/go-libfossil` from 0.11.1 to 0.12.0
- [Release notes](https://github.com/danmestas/go-libfossil/releases)
- [Changelog](https://github.com/danmestas/go-libfossil/blob/main/CHANGELOG.md)
- [Commits](danmestas/go-libfossil@v0.11.1...v0.12.0)

---
updated-dependencies:
- dependency-name: github.com/danmestas/go-libfossil
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go_modules
- dependency-name: github.com/danmestas/go-libfossil
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go_modules
- dependency-name: github.com/danmestas/go-libfossil
  dependency-version: 0.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: go_modules
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Oct 16, 2026
@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 16, 2026

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
✅ Deployment successful!
View logs		 edgesync-docs 567f524 Commit Preview URL

Branch Preview URL		 Oct 16 2026, 06:14 PM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants