0.5.27: Pi 1.0.3, Azure provider rename - #325
Merged
Merged
Conversation
Pi 1.0.3 renamed azure-openai-responses to azure, so feynman model login would have saved Azure credentials under a provider no model uses. A test now checks every API-key provider Feynman offers against Pi's providers.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
refresh_token_invalidatedafter a cancelled refresh and EIO crash reports on terminal close; fullscreen transcript top/bottom move to Ctrl+Home/End.azure-openai-responses→azure: Feynman's API-key setup and provider labels now useazure. New test checks every API-key provider Feynman offers exists in Pi (fails before the rename on 1.0.3). Telemetry shows no Azure users in 14 days, so no migration code; release notes say how to move an existing setup.Checked and not changed: pi-web-access 0.36.0's markdown-first fetch (
HTTP 4068 times for one 0.5.26 install). Over 30 publisher, preprint, docs, and code sites, the markdown-first and browser Accept headers returned identical status codes, so I could not tie the 406 to the new header.Verified: tsc, npm test (336 pass), check-pi-rpc, clean consumer install (no ERESOLVE, audit clean, RPC clean), website audit and build, native bundle, PTY on Pi 1.0.3 (fullscreen and regular: header, /help, /quit exit 0, alternate screen entered and left in fullscreen), and a live /lit on Claude Opus 5.5 with parallel researchers: workflow on the first call, verifier and reviewer, 12 files under outputs/, nothing under subagent-artifacts.