@reventlessdev/reventless-core 3.0.0-alpha.247 โ 3.0.0-alpha.248
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +14 -0
- package/package.json +3 -3
- package/src/adapter/Auth/Auth_ActiveRole.res +15 -0
package/CHANGELOG.md
CHANGED
|
@@ -3,6 +3,20 @@
|
|
|
3
3
|
All notable changes to this project will be documented in this file.
|
|
4
4
|
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
|
|
5
5
|
|
|
6
|
+
# 3.0.0-alpha.248 (2026-08-23)
|
|
7
|
+
|
|
8
|
+
* feat(aws)!: scope the active-role store to the identity provider ([08e287d](https://github.com/ReventlessDev/reventless-core/commit/08e287db9721977b818bad76671ec4c62be6f9af))
|
|
9
|
+
|
|
10
|
+
### BREAKING CHANGES
|
|
11
|
+
|
|
12
|
+
* platform:cognitoUserPoolId is now
|
|
13
|
+
platform:identityProviderId (REVENTLESS_IDENTITY_PROVIDER_ID). The old
|
|
14
|
+
spelling is still read and warns โ do not drop it until the new secret
|
|
15
|
+
is in place, because an unset provider id is auto mode, and auto mode
|
|
16
|
+
creates a new user pool.
|
|
17
|
+
|
|
18
|
+
|
|
19
|
+
|
|
6
20
|
# 3.0.0-alpha.247 (2026-08-22)
|
|
7
21
|
|
|
8
22
|
* feat(core)!: a slice that has given up says so ([f5559ab](https://github.com/ReventlessDev/reventless-core/commit/f5559abede3a9cf2c9a48aadc69a666c46cc75bf))
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@reventlessdev/reventless-core",
|
|
3
|
-
"version": "3.0.0-alpha.
|
|
3
|
+
"version": "3.0.0-alpha.248",
|
|
4
4
|
"description": "Core package for Reventless framework",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"jest": {
|
|
@@ -29,13 +29,13 @@
|
|
|
29
29
|
"sury": "11.0.0-rc.2",
|
|
30
30
|
"uuid": "^13.0.0",
|
|
31
31
|
"@reventlessdev/rescript-effect": "0.1.0-alpha.32",
|
|
32
|
-
"@reventlessdev/rescript-fast-csv": "2.0.0-alpha.8",
|
|
33
32
|
"@reventlessdev/rescript-hash-object": "1.2.0-alpha.14",
|
|
33
|
+
"@reventlessdev/rescript-fast-csv": "2.0.0-alpha.8",
|
|
34
34
|
"@reventlessdev/rescript-jest": "1.0.0-alpha.10",
|
|
35
35
|
"@reventlessdev/rescript-node": "2.0.0-alpha.8",
|
|
36
36
|
"@reventlessdev/rescript-pulumi-pulumi": "2.3.0-alpha.19",
|
|
37
|
-
"@reventlessdev/rescript-ssh2": "2.0.0-alpha.8",
|
|
38
37
|
"@reventlessdev/rescript-uuid": "2.0.0-alpha.0",
|
|
38
|
+
"@reventlessdev/rescript-ssh2": "2.0.0-alpha.8",
|
|
39
39
|
"@reventlessdev/reventless-infra": "3.0.0-alpha.150",
|
|
40
40
|
"@reventlessdev/reventless-interop": "3.0.0-alpha.33",
|
|
41
41
|
"@reventlessdev/reventless-spec": "3.0.0-alpha.122"
|
|
@@ -43,6 +43,21 @@ they picked stopped taking effect.
|
|
|
43
43
|
*/
|
|
44
44
|
let staleRoleClaim = "activeRoleStale"
|
|
45
45
|
|
|
46
|
+
// ๐จ **State that narrows an identity is scoped to the identity provider, not to
|
|
47
|
+
// the platform.**
|
|
48
|
+
//
|
|
49
|
+
// A provider has one minting point, and narrowing works by driving it. Keep the
|
|
50
|
+
// state a platform-scoped resource and two deployments sharing one provider each
|
|
51
|
+
// drive their own copy โ whichever holds the minting point reads state the other
|
|
52
|
+
// never writes, so a role switch reports success and changes nothing. Each half
|
|
53
|
+
// is individually correct, so nothing short of two deployments can observe it.
|
|
54
|
+
//
|
|
55
|
+
// On AWS that is a pool's single `PreTokenGeneration` slot and the
|
|
56
|
+
// `platform:activeRoleStore` that follows it; elsewhere the shape differs and the
|
|
57
|
+
// rule does not. It cannot be a `conformanceCases` entry โ those are
|
|
58
|
+
// `(membership, requested) โ expected`, and this is about *where two deployments
|
|
59
|
+
// keep state*. See [docs/plans/active-role-store-scoped-to-the-pool.md].
|
|
60
|
+
|
|
46
61
|
/**
|
|
47
62
|
The conformance table ยง6 of the plan requires: the same (membership, requested,
|
|
48
63
|
expected) cases run against both minting paths, so the two implementations cannot
|