Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly #2985

Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly

chore(ci): slow both dependabot channels from weekly to monthly #2985

Workflow file for this run

.github/workflows/changeset-presence.yml at 92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
- name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
- name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs
, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all 
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix");
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms");
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links");
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default");
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers");
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs

, 'i');
if (__m === '*' || __re.test(location.href)) {
injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode");
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();

Skip to content
 Changeset Presence

chore(ci): slow both dependabot channels from weekly to monthly
#2985
Sign in to view logs

chore(ci): slow both dependabot channels from weekly to monthly


chore(ci): slow both dependabot channels from weekly to monthly #2985
Workflow file for this run

.github/workflows/changeset-presence.yml
 at
92e5d3b
name: Changeset Presence
# Demands the DECLARATION that objectstack#4731 / #4843 made the criterion for
# "which frontend changes shipped": a change to the source of a package the
# release covers must add a `.changeset/*.md`. An empty frontmatter counts — what
# is required is one sentence written while the author still knows what the change
# does, not a release. Full rationale, the measured history, and the exemption's
# exact spelling: `scripts/check-changeset-presence.mjs`.
#
# Why this is a SECOND changeset workflow rather than a wider trigger on the
# first. `changeset-guard.yml` runs only when `.changeset/**` changes, and that
# inversion is deliberate and documented in its own header: on a PR that adds
# ONLY a changeset, every gate inside `ci.yml` and `lint.yml` skips, so nothing
# in either of them ever reads the changeset — and that guard exists to see
# exactly that PR. A PR which FORGOT its changeset does not touch `.changeset/**`
# at all, so the one check that could notice is the one guaranteed not to run.
# Widening those paths would break the case it was built for. Hence two
# workflows, opposite directions: that one polices the level of a declaration
# that exists, this one polices the existence of a declaration at all.
#
# That is no longer the reason this header used to give. It said `ci.yml` and
# `lint.yml` both list `.changeset/**` under `paths-ignore`, so a PR adding ONLY
# a changeset "starts nothing else". objectui#3523 step 2 deleted `paths-ignore`
# from their `pull_request` trigger; it remains ONLY on `push`. Such a PR does
# start both workflows and does produce their contexts — measured: PR #3856 (one
# markdown file) 16 checks, PR #4339 (one line added to AGENTS.md) 17. The
# correction is objectui#3857; an author had already acted on the old sentence
# and got the opposite result.
#
# What #3523 moved rather than deleted is the path DECISION: it is now the
# `Decide whether this change needs a full run` step in `ci.yml`, with a twin in
# `lint.yml`, and its exclusion list is that `push` filter unchanged — markdown
# and `.changeset/**` included, held identical to it by
# `scripts/__tests__/merge-queue-reporting.test.ts`. Both workflows therefore
# start, report, and skip every expensive step on precisely this PR: the
# conclusion survives its premise, and `changeset-guard.yml`, running outside
# that in-job switch with no install and no build, is still the only thing that
# judges a changeset-only PR at all.
#
# Hence also: no `paths` and no `paths-ignore` here, deliberately — the same
# choice `control-bytes.yml` and `docs-links.yml` made and for a stronger reason.
# A path filter on the trigger skips the WHOLE workflow (GitHub has no per-job
# path filter), so the context is never CREATED on a pull request that does not
# match, and a required context that is never created leaves the PR pending rather
# than failing it — in the queue, until the ruleset's 60-minute timeout. That is
# objectui#3523's second half, and it is why the four gates moved their filters
# into the jobs. This gate reports on every pull request instead: it decides from
# the diff, inside the script, and says so when nothing is owed. A `paths` filter
# would additionally be a second copy of the script's guarded surface, free to
# drift from it — and the surface is derived from `.changeset/config.json`
# precisely so there is only one. `scripts/__tests__/check-changeset-presence.test.ts`
# fails if a filter is ever added.
#
# It needs no install and no build — a checkout, `setup-node`, and one `node` call
# over `git diff` — so keep it that way if you add checks to it.
on:
pull_request:
branches: [main, develop]
# Merge queue (objectui#3523 — see `ci.yml`'s trigger block for the full note
# and the measurements behind it). A required context that does not report on a
# queue build stalls the queue until the ruleset's 60-minute status-check
# timeout fails it, so a gate that carries no path filter — and therefore CAN
# be required — has to subscribe. `types:` is named although `checks_requested`
# is currently the only one GitHub defines.
#
# The script needs no per-event branch to work here: it resolves the base as
# the merge base with the target branch, and on a queue build (no
# `GITHUB_BASE_REF`, no `github.event.pull_request`) that falls through to the
# merge base with `origin/main`, which is the commit the queue built the group
# on. `ci.yml`'s `pnpm check:i18n-drift` step already resolves its base exactly
# this way on this event.
merge_group:
types: [checks_requested]
# Deliberately NOT subscribed:
#
# - `push` to `main`. There is nothing left to demand: the change has landed,
# and failing the push would only paint `main` red at the author of the next
# commit. The pull request and the queue build are where a declaration can
# still be written.
# - `workflow_dispatch`. A manual run has no revision range to judge, and this
# gate fails loudly rather than inventing one. Locally it is
# `node scripts/check-changeset-presence.mjs`, which defaults to this branch
# against its merge base and reads the working tree, so an author gets the
# answer before committing.
concurrency:
group: changeset-presence-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: true
permissions:
contents: read
jobs:
changeset-presence:
name: Changeset Declaration
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
 - name: Checkout code
uses: actions/checkout@v7
with:
# The gate compares this change against its MERGE BASE with the target
# branch, so it needs history — checkout's default is a depth-1 clone
# where `git merge-base` has nothing to find. An unresolvable base is a
# hard failure in the script, never a skip, so getting this wrong is a
# red build rather than a silent pass; it is spelled out here so it
# stays that way. Same requirement, same reason, as the `fetch-depth: 0`
# on `ci.yml`'s `type-check` job for `pnpm check:i18n-drift`.
fetch-depth: 0
 - name: Setup Node.js
uses: actions/setup-node@v7
with:
node-version: '22.x'
# Reads `.changeset/config.json` and `git diff`, and nothing else — no
# install, no network. The guarded surface is every workspace package named
# in the `fixed` group, so it follows the release configuration instead of
# being a hand-written glob: `@object-ui/console` lives at `apps/console`,
# outside `packages/`, and is both the most-edited published package here
# and the one the platform's `bump-objectui.sh` writes a changeset for.
 - name: Verify a changeset declares this change
run: node scripts/check-changeset-presence.mjs