PerishLab/ensign
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Advance ensign to 0.2.0 #57

Merged
PerishFire merged 1 commit from land/ship-face into main 2026-07-31 05:19:43 +00:00
Conversation 0 Commits 1 Files changed 3 +5 -5
PerishFire commented 2026-07-31 05:16:04 +00:00
Owner
Copy link

release: advance ensign to 0.2.0

0.1.3 is already on the registry and ship is idempotent by version, so it
would have reported every artifact pushed and left the old binary serving.

0.2.0 rather than a patch. One unit became three: Actor keeps what ensign
decides about a person, Profile what the world may see, Source one way
of signing in, and Pass roots at the Source rather than the person. The
subject in a token is an opaque value rather than a row id. An access token
carries the audience it was requested for instead of the issuer. The
configuration file is named for this product rather than for keel.

Nothing that ran against 0.1.3 runs against it unchanged, and no store from
it can be opened — the estate is rebuilt, which costs nothing because none
was ever deployed.

release: advance ensign to 0.2.0 0.1.3 is already on the registry and ship is idempotent by version, so it would have reported every artifact pushed and left the old binary serving. 0.2.0 rather than a patch. One unit became three: `Actor` keeps what ensign decides about a person, `Profile` what the world may see, `Source` one way of signing in, and `Pass` roots at the Source rather than the person. The subject in a token is an opaque value rather than a row id. An access token carries the audience it was requested for instead of the issuer. The configuration file is named for this product rather than for keel. Nothing that ran against 0.1.3 runs against it unchanged, and no store from it can be opened — the estate is rebuilt, which costs nothing because none was ever deployed.
Advance ensign to 0.2.0
All checks were successful
guard / guard (pull_request) Successful in 3m31s
Details
guard / guard (push) Successful in 3m15s
Details
37d820b924 
release: advance ensign to 0.2.0

0.1.3 is already on the registry and ship is idempotent by version, so it
would have reported every artifact pushed and left the old binary serving.

0.2.0 rather than a patch. One unit became three: `Actor` keeps what ensign
decides about a person, `Profile` what the world may see, `Source` one way
of signing in, and `Pass` roots at the Source rather than the person. The
subject in a token is an opaque value rather than a row id. An access token
carries the audience it was requested for instead of the issuer. The
configuration file is named for this product rather than for keel.

Nothing that ran against 0.1.3 runs against it unchanged, and no store from
it can be opened — the estate is rebuilt, which costs nothing because none
was ever deployed.

Land-Source: ship-face@0e1a53d4620f13d85d600a2eab5b3d386637ab6d
PerishFire deleted branch land/ship-face 2026-07-31 05:19:43 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/ensign!57
No description provided.