Skip to content

chore: release master - #894

Merged
totollygeek merged 1 commit into
masterfrom
release-please--branches--master
Oct 21, 2026
Merged

totollygeek merged 1 commit into
masterfrom
release-please--branches--master

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

core: 1.77.0

1.77.0 (2026-10-21)

Features

  • core: cache SDK outputs with their .git, long paths and a raised size limit (#893) (216de10)
  • core: keep tar and zip file modes and zip symlinks on extraction (#891) (a9d3933)

Bug Fixes

  • core: speed up tar.xz extraction with the system xz (#892) (f86689d)

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--master branch from 80fa55a to 26045a2 Compare October 21, 2026 17:50
@github-actions
github-actions Bot force-pushed the release-please--branches--master branch from 26045a2 to c247021 Compare October 21, 2026 18:15
@zuke-build

zuke-build Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

🤖 Zuke AI review

🔎 AI review — review

✅ Passed — no findings.

Reviewer Verdict Score Severity Findings
🛡️ security review ✅ passed 0/10 none 0
🧹 generic review ✅ passed 0/10 none 0
🛡️ security review — ✅ passed · 0/10

Score: 0/10 · Severity: none · 0 finding(s)

Tokens: 27721 in · 42 out · 27763 total

Budget: 27,763 tokens of 500,000 tokens

Commands

Only comments from maintainers the host itself attributes as such are read; anyone else's are ignored before anything sees them.

Say What happens
@zuke-build review Runs the review again now, with no push: every rebuttal is adjudicated and answered where it was made.
@zuke-build accept <id> <reason> Accepts a finding as intended for this pull request: it is recorded with your reason, its thread is closed, and no reviewer raises it again here — reworded, moved to another file or escalated. In the finding's own thread the id may be left out.
Reply in a finding's thread, or quote its id in a comment Contests it: the next run re-checks the finding against your argument and dismisses it when the argument holds, or says what is missing.

No security-relevant changes were introduced; the diff only bumps the core package version and changelog entries.

🧹 generic review — ✅ passed · 0/10

Score: 0/10 · Severity: none · 0 finding(s)

Tokens: 10043 in · 35 out · 10078 total

Budget: 37,841 tokens of 500,000 tokens

Commands

Only comments from maintainers the host itself attributes as such are read; anyone else's are ignored before anything sees them.

Say What happens
@zuke-build review Runs the review again now, with no push: every rebuttal is adjudicated and answered where it was made.
@zuke-build accept <id> <reason> Accepts a finding as intended for this pull request: it is recorded with your reason, its thread is closed, and no reviewer raises it again here — reworded, moved to another file or escalated. In the finding's own thread the id may be left out.
Reply in a finding's thread, or quote its id in a comment Contests it: the next run re-checks the finding against your argument and dismisses it when the argument holds, or says what is missing.

Version metadata was bumped consistently across the core package with no behavioral changes.

@totollygeek
totollygeek merged commit 0aa9fe0 into master Oct 21, 2026
18 of 20 checks passed
@totollygeek
totollygeek deleted the release-please--branches--master branch October 21, 2026 19:16
@zuke-build

zuke-build Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

🤖 Created releases:

🌻

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant