Skip to content

Web Console 1.6.167

Choose a tag to compare

View all tags
@chen21019 chen21019 released this 02 Oct 13:35
Immutable release. Only release title and notes can be modified.
1.6.167
This tag was signed with the committer’s verified signature.
chen21019 Cheng-Chen, Chen
SSH Key Fingerprint: nF0fDZ8EQGL+GjPXONcQ9qd4VseNYmcscqwvax867AE
Verified
Learn about vigilant mode.
dff35fc
This commit was signed with the committer’s verified signature.
chen21019 Cheng-Chen, Chen
SSH Key Fingerprint: nF0fDZ8EQGL+GjPXONcQ9qd4VseNYmcscqwvax867AE
Verified
Learn about vigilant mode.

Web Console 1.6.167

The shared API store now normalizes IDs only when looking up the already-normalized schema group. Mixed-case resource types such as registryCredential resolve their actual cached permission schema. Ordinary resource IDs remain opaque and case-sensitive; missing schemas remain denied and separate project stores are not combined. Backend authorization, API schemas, authentication and lifecycle request methods are unchanged.

Validated source: dff35fc4bce340e21cac7204146a7bcb20a7b60b.

Exact-source validation 37012345421 passed 772/772 actual tests, with zero failures, skips or todo cases. Four new tests exercise the actual Store bulk cache, inherited Resource getter, capability consumers, project isolation and case-sensitive resource IDs. The focused local Chrome run passed 4 tests and 43 assertions. Two production builds produced byte-identical archives; this release reuses that candidate without rebuilding.

Archive SHA-256: e8e714fc06282de75a3570aac1d4d4d04a3c9478d982d0d5aaeae14efa8ebbaf (2,976,297 bytes). The accompanying SHA-256 file uses the portable archive basename. The numeric signed tag pins the validated source; no existing tag or artifact is overwritten. The API-store compatibility archive advances from revision 3 to 4, retaining its upstream version, license and dependency graph.

This is component publication only, not Server packaging/deployment, complete resource/role/language-matrix acceptance, packaged native-browser acceptance or a zero-vulnerability claim. Historical HOLD evidence is unchanged. Security thresholds and dependency versions are unchanged.

Assets 5
Loading