Skip to content

Release AMKernel 0.1.3 #136

Closed
Closed

Description

@houlianpi

Goal

Publish owner-requested AMKernel 0.1.3 from protected main.

Contract

Update pyproject.toml and uv.lock to 0.1.3; date the existing unreleased changelog without expanding support claims. Preserve unrelated local evidence deletions and .gitignore changes outside this release PR. Obtain independent review, pass PR checks, merge through protected main, and require successful exact-main CI quality/package-smoke/all compatibility jobs. Dispatch Release with that CI run ID to publish the retained tested wheel and evidence assets as immutable v0.1.3 and to PyPI.

Acceptance

Version metadata and installed-wheel smoke report 0.1.3. Record PR, exact main commit, successful CI and Release run URLs, immutable GitHub release assets/checksums, and matching PyPI wheel digest. Ubuntu/macOS CPython 3.11–3.13 remain the only qualified support claim; mobile remains experimental and Windows unqualified.

Activity

  1. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    Release candidate commit: 7da3c9e on release/0.1.3. Only pyproject.toml, uv.lock and CHANGELOG.md changed; dependency resolutions unchanged. Independent architecture/security review: 0 findings (reviewed metadata, changelog extraction, support limits, exact-CI artifact release path). Local uv lock --check and build passed; tests/test_release.py: 10 passed; clean installed-wheel package_smoke passed with runtime version 0.1.3. Initial smoke stopped before installation because the isolated worktree inherited an old 0.1.1 wheel; preserved that copied artifact outside dist and then completed the smoke with only the candidate wheel. Local wheel SHA-256: 82eb6be1d36ac00e4ee2d158ec0ecf3a61db81bc134315ecc96300b4153bf847 (not a publication artifact). Authoritative hosted PR/main CI and publication are still required.

    Project #2 item creation was attempted but the available token lacks project write scope; no board change is claimed. Release tracking remains in this issue.

  2. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    Release PR: #137. Candidate 7da3c9e uploaded via GitHub REST git database after git HTTPS could not reach github.com:443; uploaded tree and commit SHA exactly match the locally reviewed/tested candidate. PR CI is running; no gate bypass or publication dispatch yet.

  3. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    PR #137 merged through protected main at 4f3bde3 after every PR check passed (CI 42030170128, all six compatibility jobs plus quality/package-smoke; supplementary cross-OS process checks also passed). Waiting for authoritative exact-main CI before dispatching Release.

  4. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    0.1.3 published successfully: Release run https://github.com/FSQ-lab/amkernel/actions/runs/42033385692 used authoritative main CI https://github.com/FSQ-lab/amkernel/actions/runs/42031757774 at 4f3bde3. Immutable GitHub release https://github.com/FSQ-lab/amkernel/releases/tag/v0.1.3 has exactly the tested wheel plus archive and manifest. Downloaded release asset digests equal authoritative CI digests: wheel 82eb6be1d36ac00e4ee2d158ec0ecf3a61db81bc134315ecc96300b4153bf847; archive 4e99132a5d208e8afc6829d759b264f325c7d2c5f18d594394cc2b2e781207e0; manifest 57bb03c267909f52bf9ef367eca0ba1e1987edca6af04b367e1361f093c2df27. PyPI 0.1.3 JSON reports the identical wheel digest. A fresh external project installed amkernel==0.1.3 directly from https://pypi.org/simple; --version and the complete installed_stdio MCP lifecycle/output/cleanup scenario passed with public-index dependencies. Original local main fast-forwarded to release commit without touching existing evidence deletions/.gitignore edits.

    README still names the previous preview in its title/latest links; correcting those repository-facing entry points in a docs-only PR. The immutable 0.1.3 wheel retains its original README long description; package metadata and CLI correctly report 0.1.3. No asset overwrite or version reuse.

  5. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    Additional provenance verification passed: uvx --from pypi-attestations pypi-attestations verify pypi --repository https://github.com/FSQ-lab/amkernel /tmp/amkernel-0.1.3-published/amkernel-0.1.3-py3-none-any.whl returned OK: amkernel-0.1.3-py3-none-any.whl. This verifies the actual downloaded GitHub-release wheel against the PyPI attestation and expected repository identity. README latest-version correction is PR #138 (four lines only); checks pending.

  6. houlianpi commented on Nov 5, 2026

    @houlianpi
    ContributorAuthor

    Release acceptance completed: protected-main release PR #137, successful exact-main CI 42031757774, successful Release 42033385692, immutable v0.1.3 assets and PyPI publication, identical wheel SHA-256, verified PyPI attestation for the expected repository, and fresh public-index install plus complete MCP smoke. README entry-point correction PR #138 also merged after all hosted checks passed. Original local edits remain excluded. Project board write remains unavailable due token scope; no board update claimed.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions