Reconnexion/ng-eventually-refine-providers
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Pin the engagement by version, at 1.0.0-dev.15

Browse Source 
The Change policy asks for a tag carrying the package name, and one now
exists for this version, so the pin moves off the authoring branch onto
`polyfill/v1.0.0-dev.15`.

That version answers standing requests of its own: a read of a document
named in `graphs` now reaches it before the query opens, a shape query
hands back the shape's objects rather than property bags, and the leaf
gained an "Asked for, not decided" list where an application's request
leaves a trace instead of living in a message.
This commit is contained in:
Sylvain Duchesne
2026-10-01 19:54:36 +02:00
parent dcde2859fe
commit 6875d8b353
2 changed files with 79 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.project/contracts.yaml
+3 -7
View File
@@ -18,11 +18,7 @@ consume:
- contract: polyfill-surface
type: git
pullFrom: git@gitea.reconnexion.apps.gueraud.net:Reconnexion/ng-eventually.git/.project/concepts/app-contract/polyfill-surface/contract_polyfill-surface.md
# The Change policy names the pin regime — a tag carrying the package name
# (`polyfill/vX.Y.Z`), since that repo publishes two engagements — and names
# `1.0.0-dev.14` as what to pin. That tag does not exist: only `polyfill/v1.0.0-dev.2`
# and `-dev.3` are posted, so the announced version is not referenceable. Pinned on the
# branch the engagement is authored on until the tag is cut; declared as a friction in
# `usage_refine-providers-eventually.md`, not worked around.
ref: caps-p1a-and-virtual-user-boundary
# The Change policy names the pin regime: a tag carrying the package name, since that
# repo publishes two engagements whose versions move independently.
ref: polyfill/v1.0.0-dev.15
into: concepts/refine-binding/polyfill-surface/