Skip to content

chore: setup ci#5

Merged
felipefreitag merged 17 commits into
mainfrom
setup-ci
Mar 10, 2026
Merged

chore: setup ci#5
felipefreitag merged 17 commits into
mainfrom
setup-ci

Conversation

@felipefreitag

Copy link
Copy Markdown
Contributor

No description provided.

@felipefreitag felipefreitag changed the title chore: Setup ci chore: setup ci Mar 9, 2026
Comment thread biome.json Outdated
Comment thread package.json Outdated
Comment thread package.json Outdated
Comment thread package.json Outdated
Comment thread .github/workflows/ci.yml Outdated
Comment thread .github/workflows/ci.yml Outdated
@felipefreitag felipefreitag merged commit 3489931 into main Mar 10, 2026
4 checks passed
@felipefreitag felipefreitag deleted the setup-ci branch March 10, 2026 15:48
dielduarte added a commit that referenced this pull request Jun 25, 2026
Felipe review (#5): migrateRawProfile cast oauth_grant entries with `as` and no
validation, so a hand-edited or corrupted file would surface inconsistent state
later. Require a string scope, and require token fields (when any are present) to
form a complete, well-typed grant; throw CorruptedCredentialsError otherwise.
Metadata-only secure-storage entries (scope only) remain valid.
dielduarte added a commit that referenced this pull request Jun 25, 2026
Refines #5: throwing CorruptedCredentialsError when an oauth_grant had partial or
wrong-typed token fields made one bad profile unreadable for the whole file. Real
files written by older clients can carry e.g. refresh_token_expires_at: null.
Instead, drop invalid token fields during read so the profile degrades to a
re-login while the rest of the file stays usable; the grant is still validated at
point-of-use (resolveAuthentication / parseOAuthGrantBlob).
dielduarte added a commit that referenced this pull request Jul 3, 2026
Felipe review (#5): migrateRawProfile cast oauth_grant entries with `as` and no
validation, so a hand-edited or corrupted file would surface inconsistent state
later. Require a string scope, and require token fields (when any are present) to
form a complete, well-typed grant; throw CorruptedCredentialsError otherwise.
Metadata-only secure-storage entries (scope only) remain valid.
dielduarte added a commit that referenced this pull request Jul 3, 2026
Refines #5: throwing CorruptedCredentialsError when an oauth_grant had partial or
wrong-typed token fields made one bad profile unreadable for the whole file. Real
files written by older clients can carry e.g. refresh_token_expires_at: null.
Instead, drop invalid token fields during read so the profile degrades to a
re-login while the rest of the file stays usable; the grant is still validated at
point-of-use (resolveAuthentication / parseOAuthGrantBlob).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants