docs: move the atomicassets-api baseline to the tagged 2.2.0 release - #19
Merged
Conversation
The baseline read an untagged main state while the repo now tags releases and both hosted deployments report 2.2.0 on /health. Of the cited files, fifteen are byte-identical to the old pin; the one behavior change is that the template-buyoffer socket handler went from defined-but-unwired to wired, which two pages asserted the other way around as a sourced fact, so those sections now state the creation-only broadcast. A mainnet schema read also shows the mediatype synthesis live fleet-wide, retiring the pre-2.0 mainnet note.
robrigo
force-pushed
the
docs/api-tagged-baseline
branch
from
August 18, 2026 21:56
7df2a5f to
489c7dc
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.
What this change claims, in one sentence:
The atomicassets-api baseline moves from an untagged main state to tag
2.2.0(the version both hosted deployments report on/health), and the one behavior change since the old pin, the template-buyoffer socket handler going from defined-but-unwired to wired, is stated where two pages asserted the opposite.Source:
atomicassets-apitag2.2.0= commitcf8bf323= current main;f6419858is its ancestor, 46 commits back; of the twenty-one cited files, fifteen are byte-identical across that span. Wiring:src/api/namespaces/atomicmarket/index.ts:187-190registerstemplateBuyofferSockets;src/api/namespaces/atomicmarket/routes/template-buyoffers.ts:127-170emitsnew_template_buyofferonlognewtbuyoonly, same subscribe-room pattern as the other market namespaces. Live:GET /healthonwax.api.atomicassets.ioandtest.wax.api.atomicassets.ioboth report2.2.0, and a mainnet schema read returns the synthesizedmediatype/infofields, retiring the pre-2.0 mainnet note inreference/atomicassets/tables.md. The README's baselines copy also syncs its stale api and SDK lines to the ledger.Tier: both for the corrected socket and deployment facts; other pages are textual re-pins.
Row in
reference/validation.mdupdated: yes; the baseline line, the api-streaming row pin and note, and the api.md row note move together. The CHANGELOG section assumes this merges after #17 and #18; expect trivial conflicts on CHANGELOG.md and the baselines blocks as those land, which I will rebase away.