8000 Update kittyview to 0.1.5 by gominimal-pkgmgr-mgr[bot] · Pull Request #701 · gominimal/pkgs · GitHub
[go: up one dir, main page]

Skip to content

Update kittyview to 0.1.5 - #701

Merged
bryan-minimal merged 2 commits into
mainfrom
update-kittyview-0.1.5
Sep 16, 2026
Merged

bryan-minimal merged 2 commits into
mainfrom
update-kittyview-0.1.5

Conversation

@gominimal-pkgmgr-mgr
Copy link
Copy Markdown
Contributor

Update kittyview 0.1.4 → 0.1.5

Source: github:gominimal/kittyview:operator-pinned
Release: https://github.com/gominimal/kittyview/releases/tag/v0.1.5
Changelog: gominimal/kittyview@v0.1.4...v0.1.5
Released: 12 days ago (2026-09-03)

Pkgscan: clean — diff against the prior version surfaced no newly-introduced suspicious patterns.

Components changed

CycloneDX component delta (declared materials — the package's own version, not a dependency-tree diff)
Component Old New
~ kittyview 0.1.4 0.1.5
~ kittyview-upstream 0.1.4 0.1.5

Changes

Old New
Version 0.1.4 0.1.5
SHA256 33e65aafea329545... 8e234b41d31d1aae...
Size 59 KB
Source https://github.com/gominimal/kittyview/archive/refs/tags/v0.1.4.tar.gz https://github.com/gominimal/kittyview/archive/refs/tags/v0.1.5.tar.gz
  • License: Apache-2.0 (source: GitHub + tarball)

Quality suggestions

  • Missing tests block. This package has no standalone tests, so the buildbot will only verify compilation — not functional correctness. Consider adding a minimal smoke test (e.g., a --version or small round-trip invocation) as part of this PR so future bumps catch regressions. See packages/python/build.ncl for a simple example.

Created by pkgmgr

@coderabbitai
coderabbitai Bot commented Sep 15, 2026 •
Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 0ac9b379-5a90-475c-abc0-b0c05b6f293f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

… failure)

The 2026-09-15T22:06 run failed with:

  Run failed: failed to connect to RES: res-server VM res-server-arm64 could
  not start: no capacity in zone us-west1-a (GCE stockout) after retrying for
  240s — transient, re-trigger to retry

Nothing in this PR is implicated. amd64 built kittyview 0.1.5 cleanly
("Finished `release` profile ... in 17.76s"), uploaded to the shared cache,
passed all 15 package checks and a 476-entry cache audit. arm64 never started
a build at all — the VM could not be allocated.

Branch is 0 commits behind main, so this re-runs against current main rather
than a stale tree.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@bryan-minimal
bryan-minimal added this pull request to the merge queue Sep 16, 2026
@github-merge-queue
github-merge-queue Bot removed this pull request from the merge queue due to no response for status checks Sep 16, 2026
@bryan-minimal
bryan-minimal added this pull request to the merge queue Sep 16, 2026
Merged via the queue into main with commit 48f8d38 Sep 16, 2026
11 checks passed
@bryan-minimal
bryan-minimal deleted the update-kittyview-0.1.5 branch September 16, 2026 16:07
bryan-minimal added a commit that referenced this pull request Sep 16, 2026
Brings in #701 (kittyview) and #636 (AGENTS.md docs canary). Neither touches
mono, so this is not expected to fix the arm64 failure on its own — the branch
was BEHIND main by 2 and a re-run on a stale tree gives a fresh timestamp
rather than fresh signal (the lesson from #669).

Re-running to establish whether mono's arm64 SIGSEGV is deterministic. amd64
built the full closure green in the last run (7185 checks, 476 cache entries);
only arm64 failed, inside mono's own AOT step. This PR touches only
packages/coreutils/build.ncl.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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

0