Skip to content

docs: refresh ORM 0.5.0 qualification status #61

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
smiggleworth merged 1 commit into from
Oct 13, 2026
Merged

docs: refresh ORM 0.5.0 qualification status #61

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,9 @@
- Gate real and normally installed generation/validation/no-op workflows against
isolated PostgreSQL 16, 17 and 18 scratch databases.

### Remaining release gate
### Candidate verification

- Complete coordinated 0.5.0 packed-candidate and website qualification remains
pending. Maintainer review and approval are required before publication.
- The exact promotion candidate on PR #58 passes the Linux, macOS and Windows
package gates, PostgreSQL 16–18 integration and installed-generation checks,
and CodeQL. Tag creation and npm publication run through the main-branch
package workflow.
2 changes: 1 addition & 1 deletion docs/0.5.0-api.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# 0.5.0 ORM API decisions

Status: implementation candidate; API issue #53 remains open for the complete 0.5.0 packed-package and generated website review. The real PostgreSQL tooling fix for [#55](https://github.com/askrjs/askr-orm/issues/55) has separate native and installed workflow qualification in [PostgreSQL tooling](postgres-tooling.md).
Status: the API contraction was delivered by merged PR #56, and issue #53 is closed. The exact 0.5.0 promotion candidate is covered by the packed-package contract and hosted checks on [PR #58](https://github.com/askrjs/askr-orm/pull/58). The real PostgreSQL tooling fix tracked by [#55](https://github.com/askrjs/askr-orm/issues/55) is qualified in [PostgreSQL tooling](postgres-tooling.md). This document records package API decisions and migration guidance.

The published 0.4.0 declarations expose 132 entrypoint/name pairs. The curated contract exposes 78: 68 root names, one CLI bridge, seven PostgreSQL names and two SQLite names. There are 54 removed named exports, plus the removed `sql.key` member. No compatibility shims are provided.

Expand Down
5 changes: 1 addition & 4 deletions docs/0.5.0-hardening.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
# 0.5.0 ORM hardening evidence

Status: the API/runtime candidate and real PostgreSQL tooling fix are qualified
locally. PostgreSQL 16–18 hosted and installed workflow checks must pass before
#55 closes. The package is **not release-ready**: #53 and #54 still require the
complete coordinated candidate/website qualification and maintainer review.
Status: issues #53, #54 and #55 are closed with the API, runtime and real PostgreSQL workflow evidence recorded below. The exact 0.5.0 promotion head on [PR #58](https://github.com/askrjs/askr-orm/pull/58) passes the Linux, macOS and Windows package gates, PostgreSQL 16–18 integration and installed-generation checks, and CodeQL. Tag creation and npm publication run through the main-branch package workflow.

## Assertion review and real adapters

Expand Down
Loading