Skip to content

Minco 1.2.0

Choose a tag to compare

View all tags
@xicv xicv released this 10 Aug 07:00
· 55 commits to main since this release
v1.2.0
48df3cc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Minco 1.2.0 closes the release-bound delivery-evidence loop and ships the complete 33-crate Minco family from one immutable source tree.

Highlights:

  • Frontend-neutral browser and native-client HTTP compatibility, including lifecycle metadata, CORS conditional requests, bearer challenges, and bounded retry guidance.
  • Verified direct object uploads with authorization-first issuance, UUIDv7 keys, media/size/SHA-256 policy, exact S3 POST signing, and explicit cleanup/content-safety boundaries.
  • Release-bound feedback task conversion with digest approval, create-only immutable receipts, and inert attachment storage.
  • Deterministic cargo minco handover JSON and Markdown packets bound to release, deployment, source, ProjectView, performance/provider ledgers, and feedback receipts.
  • Topology-aware Plan validation and cost evidence; unsupported Lambda Function URL combinations now fail before provider rendering.
  • Rich observable mail through local Mailpit and Amazon SES v2, with bounded MIME, acceptance receipts, safe tags, and policy-gated delivery-event normalization.
  • Owned loopback PostgreSQL and Rustack lifecycle support for cargo minco dev, including identity checks, durable receipts, recovery, and foreign-resource refusal.
  • The complete Signal documentation website and versioned 1.2.0 manual.
  • A local-first release boundary: authoritative quality, runtime, recovery, load, and E2E qualification remain local; GitHub Actions is bounded to exact-tag publication, Pages, and clean-Linux compatibility.

Compatibility:

  • This is an additive minor release for existing Minco 1.x applications.
  • Existing notification and object-storage APIs remain available; rich mail and managed uploads are opt-in.
  • Official plugin core compatibility advances in lock-step to ^1.2.0 without changing descriptor or capability schema versions.
  • See docs/adoption/1.1.0-to-1.2.0.md for migration and rollback guidance.

Provenance:

  • Tag: v1.2.0
  • Release commit: 48df3cc
  • Git tree: 4269d98bab1e5b02f531610f5b121727a5e186f7
  • Source-tree SHA-256: 07846817724cca504b7deff8c80006a00930cf4d37513cc88b8aeac285a15933
  • Source-manifest file SHA-256: 11df3883960a786a6112ed165f64b57914ed0a7c172c6bb969b58ac2b9515c75
  • Publication workflow: https://github.com/xicv/minco/actions/runs/31362919458
  • All 33 exact 1.2.0 crates were independently verified present and non-yanked after publication.

Evidence boundaries:

  • No live AWS application resources were created, changed, or deleted for this release.
  • Exact-tree hosted Linux performance evidence remains NOT RUN and is not a production SLO.
  • Current exact-source live-provider evidence remains unavailable; historical provider evidence stays stale.
  • Planned M14-T09 upload profiles remain deferred.
  • Package publication, docs deployment, provider qualification, and production application deployment are separate evidence states.
Assets 2
Loading