Skip to content
This repository was archived by the owner on Apr 15, 2026. It is now read-only.

222 allow jwt based authentication at sdk#225

Open
theKosmoss wants to merge 2 commits intodevfrom
222-allow-jwt-based-authentication-at-sdk
Open

222 allow jwt based authentication at sdk#225
theKosmoss wants to merge 2 commits intodevfrom
222-allow-jwt-based-authentication-at-sdk

Conversation

@theKosmoss
Copy link
Copy Markdown
Contributor

No description provided.

… storage, and fellowship ID; implement thread storage in API after game creation. Update utility functions to support JWT token retrieval and API interactions.
@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Nov 27, 2025

🦋 Changeset detected

Latest commit: 47cc8ca

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@peeramid-labs/sdk Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Nov 27, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 222-allow-jwt-based-authentication-at-sdk

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

  • Provide your own instructions using the high_level_summary_instructions setting.
  • Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
  • Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

  1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
  2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
  3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
  4. 📊 Contributor Summary — Include a Markdown table showing contributions:
    | Contributor | Lines Added | Lines Removed | Files Changed |
  5. ✔️ Additional Notes — Add any extra reviewer context.
    Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.


Comment @coderabbitai help to get the list of available commands and usage tips.

@theKosmoss theKosmoss requested a review from peersky November 27, 2025 11:10
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant