Repository navigation
build(deps): pin dms and interface-dms to the dms 14e671d tarballs - #110
Merged
Merged
Conversation
… tarballs dms 14e671d (dms#703) is the integration tip after the main merge; interface-dms 14e671d serves count/batch as GET, as dms 14e671d's frontend asks.
Member
Author
Verdict: dms-database PR 110 (re-pin to dms 14e671d)Head: 23b27fd, base campaign/integration (aa64765, its parent), MERGEABLE. Fresh clone at that sha. A single commit on integration, so there is no merge to check.
Common checks (all four re-pin PRs)
Verdict: PASS. gate-verdict: PASS 23b27fd |
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
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.
Why
The dms-* modules prove themselves against the unreleased dms of campaign/integration. This re-pins that dms to the integration tip after the main merge, so this module gets main's presenter, the permissions fix (AntelopeJS/dms#700, via AntelopeJS/dms#703) and an interface-dms whose
count/batchroute matches the frontend's GET.What changed
@antelopejs/dmspinned toantelopejs-dms-14e671d.tgz(AntelopeJS/dms 14e671d50a8495393590d2b8a077494d4a16fb6c, sha256ce4020236624bd245a7541a2d917e74f2270eee67e200ecbd89524607b33009b). It is packed withTGZ_OPTIONAL_RANGESso the optional@antelopejs/interface-dms-automationkeeps its range>=0.4.0 <1.0.0.@antelopejs/interface-dmspinned toantelopejs-interface-dms-14e671d.tgz(same commit, sha256d002a240e70558d62fdf9d8f5789604f834978281036b7f3bbf47ade1b194b06). It registerscount/batchas GET.use-tgz.sh, replacing dms 4358eef and the previous interface-dms tarball.Proofs
GITHUB_BASE_REF=campaign/integration pnpm run checkson 23b27fd:Checks: 8 passed, 0 failed.verify-tgz.sh .campaign/tgz index.tsvprints nothing.Attention