Skip to content

chore(deps): bump actions/attest-build-provenance from 2.4.0 to 4.2.2 - #4

Closed
dependabot[bot] wants to merge 7 commits into
mainfrom
dependabot/github_actions/actions/attest-build-provenance-4.2.2
Closed

dependabot[bot] wants to merge 7 commits into
mainfrom
dependabot/github_actions/actions/attest-build-provenance-4.2.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 8, 2026

Copy link
Copy Markdown

Bumps actions/attest-build-provenance from 2.4.0 to 4.2.2.

Release notes

Sourced from actions/attest-build-provenance's releases.

v4.2.2

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.1.1...v4.2.2

v4.1.1

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.1.0...v4.1.1

v4.1.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

Full Changelog: actions/attest-build-provenance@v4.0.0...v4.1.0

v4.0.0

[!NOTE] As of version 4, actions/attest-build-provenance is simply a wrapper on top of actions/attest.

Existing applications may continue to use the attest-build-provenance action, but new implementations should use actions/attest instead.

What's Changed

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

racstan and others added 7 commits October 7, 2026 22:10
- normalizeJob now keeps startAt, everyDays/Weeks/Months, dayOfMonth and
  month (validated), and schedule notes serialize them, so recurring
  schedules no longer change after a reload.
- AI-proposed follow-up jobs are created disabled, without an AI-chosen
  output path, and follow-ups cannot spawn further follow-ups.
- writeOutput rejects .., hidden and config folders, forces .md, never
  overwrites notes the plugin did not write, and drops the adapter.write
  fallback.
- Add schedule round-trip tests; fix the stale review routine id in the
  smoke test and cover the new safety checks there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Calendar "New task" jobs are registered on save (updateJob adds unsaved
  jobs with a task number); JobModal shows "New task" and validates input.
- All Run now / Run again actions use runJobNow so recurring jobs run;
  remove retryJob.
- Reviews are written once; runs without a fixed filename get a
  timestamped, titled note instead of replacing the day's output.
- cronNext uses epoch arithmetic for minutes and second truncation and
  never moves backwards, fixing the fall-back DST re-fire loop.
- Startup catch-up, initial notes sync and vault listeners run in
  onLayoutReady without blocking onload; event triggers save only when a
  job was queued.
- Schedule-note edits are parsed from the file content, not the stale
  metadata cache.
- The periodic review is rescheduled only when its cadence changes, and
  uses the periodic review model setting.
- Release attestation now runs the full check/test/smoke suite and
  verifies release assets match the build; least-privilege permissions
  and Node 22 in CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Scheduling
- Anchored every-N-days/weeks schedules count calendar days (DST-safe);
  date-only start dates are local dates; stepped schedules without a
  start date are anchored to their creation day.
- The dispatcher re-checks each due job before running it; jobs that fell
  due while the computer slept follow the startup catch-up policy.
- Periodic reviews cover files changed since the previous review and skip
  the plugin's own folders.

Execution
- Output is written before follow-ups; malformed planned/follow-up tasks
  are skipped individually.
- A reset run's late reply is discarded; Copilot runs are aborted on
  timeout; backend sends are serialized; a failed conversation rename is
  non-fatal.
- No state is saved after unload; the notes-sync timer is cleared.
- Event triggers dedupe pending events, allow a 0 cooldown and pass the
  changed path to the prompt; output history is capped at 20 files and
  the task log lists only this run's output.

UI
- Calendar pause/resume and dashboard disable go through enableJob /
  disableJob; Task view no longer waits for the AI run.
- Dashboard and calendar re-render only on state changes, not while a
  form control is focused, and keep scroll positions.
- Calendar hides occurrences before a job existed and marks past slots
  completed only with run evidence.
- Schedule-note edits reschedule only when the schedule changed.

Docs, build and CI
- Changelog entries for 2.1.7.18/2.1.7.19, newer-release lookup for
  unknown versions, and a test that the changelog matches the manifest.
- README updated to current behaviour; sentence-case lint warnings fixed.
- Production bundle is minified; actions pinned to SHAs with Dependabot.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
UI and styles
- Sentence case throughout; proper nouns restored; lint has 0 warnings.
- Keyboard and screen-reader access: clickable badges, day cells, chips
  and file rows act as buttons; labelled inputs and icon buttons;
  listbox semantics for the mention popup; labelled review-day toggles.
- CSS uses Obsidian colour variables only, no !important, a single spin
  animation, and honours prefers-reduced-motion.
- One registry for scheduler modals, closed through close() so cleanup
  runs; back buttons name their real destination.
- "Vault output" opens the last output; task view never creates notes
  for unresolved links; locale-aware times; mentions link by path.

Core
- Real cancellation: resetting a run calls Claudian cancelStreaming or
  aborts the Copilot chain; cancelled queued sends never start.
- Linear JSON extraction from AI replies (was quadratic).
- Enabling an event job no longer fires it; editing a paused task keeps
  it paused; empty review replies fail; a manual review defers the
  scheduled one; weekly schedules without days keep their weekday.
- Event names are validated and edits made during event-triggered runs
  are not replayed (no event-job ping-pong).
- Task log appended with vault.process; schedule-note migration awaited.
- Interval descriptions say the count restarts daily at the start time.

Cleanup
- Remove dead helpers and duplicate types; npm audit fix; drop the
  redundant @types/obsidian; manifest/package descriptions updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Schedule notes the user moves out of the schedules folder are followed
  (path updated) instead of being recreated there.
- Unit tests for the backend send queue, cancellation and review model,
  schedule-note frontmatter round-trip and prompts, using an obsidian
  stub aliased in the test build (67 tests).
- In-range dependency updates.
- Stop tracking the built main.js; CI and the release workflow build it
  and users get it from the release assets.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- manifest/package version 2.1.17 (x.y.z, as the Obsidian plugin review
  requires); newer than every earlier release including 2.1.16 and 2.1.8.
- versions.json keeps only x.y.z keys.
- Changelog entry for 2.1.17 (in-app and CHANGELOG.md).
- Test that the manifest version is x.y.z and listed in versions.json.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps [actions/attest-build-provenance](https://github.com/actions/attest-build-provenance) from 2.4.0 to 4.2.2.
- [Release notes](https://github.com/actions/attest-build-provenance/releases)
- [Changelog](https://github.com/actions/attest-build-provenance/blob/main/RELEASE.md)
- [Commits](actions/attest-build-provenance@e8998f9...4d10147)

---
updated-dependencies:
- dependency-name: actions/attest-build-provenance
  dependency-version: 4.2.2
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Oct 8, 2026
@racstan racstan closed this Oct 8, 2026
@racstan
racstan deleted the dependabot/github_actions/actions/attest-build-provenance-4.2.2 branch October 8, 2026 03:24
@dependabot @github

dependabot Bot commented on behalf of github Oct 8, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant