Skip to content

feat(core): read what the default build has from the schema - #3

Merged
KrimsN merged 1 commit into
mainfrom
feat/dns-79-full-build-tag
Oct 4, 2026
Merged

KrimsN merged 1 commit into
mainfrom
feat/dns-79-full-build-tag

Conversation

@KrimsN

@KrimsN KrimsN commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

dnspatch#90 adds the full build tag and a lighter default build. This makes the builder read what a release has from its schema, instead of assuming it.

  • schema.json of a release since then says in_default_build for every plugin. A plugin outside it (a notifier, rfc2136, yandexcloud, namecheap) points to the -full image; the config constructor says so under the provider cards.
  • ping_url is in every build of those releases, so it no longer points to -full and no longer adds a ping tag.
  • Schemas of older releases have no such field and are read as before: every retriever and provider in the ready-made image, ping_url and the notifiers only in -full. The bundled v0.4.4-rc.1 schema behaves exactly as it did.
  • Tests for both readings; the golden check passes against a binary built from dnspatch#90 with -tags full and the schema it generates.

Safe to merge before the dnspatch release: nothing changes until a release with the new schema is fetched (npm run schemas).

Linear: DNS-79
Part of DNS-79

…ull tag releases work

Releases since the full tag say in_default_build for every plugin. A plugin
outside it (a notifier, rfc2136, yandexcloud, namecheap) points to the -full
image, and ping_url no longer does, nor does it add a ping tag. Schemas of
older releases have no such field and are read as before.
@KrimsN
KrimsN merged commit bc22d7a into main Oct 4, 2026
2 checks passed
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.

1 participant