Skip to content

Merge main into integration/liveobjects 2025-05-08 #2581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 209 commits into from
May 8, 2025

Conversation

VeskeR
Copy link
Contributor

@VeskeR VeskeR commented May 8, 2025

Description

Merges latest main into integration/liveobjects branch to prepare for the liveobjects docs release in #2541.

The only change during conflict resolution was changing the link /docs/objects to /docs/liveobjects for the new homepage.ts structure

Checklist

dependabot bot and others added 30 commits March 21, 2025 15:44
Bumps [next](https://github.com/vercel/next.js) from 15.1.7 to 15.2.3.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v15.1.7...v15.2.3)

---
updated-dependencies:
- dependency-name: next
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
Upgrade Inkeep to latest version and apply migration changes.
…ext-15.2.3

chore(deps): bump next from 15.1.7 to 15.2.3 in /examples
[WEB-3484] fix: use character encodings for double quotes in subscribe textile to avoid processing
[WEB-4263] fix: redoc responsiveness / code block api key truncation
[WEB-4294] Persist language choice across pages
- Clarified the scope of account statistics
- Removed account stats from the REST API - there is no such API, API keys are scoped to apps only. Not sure how this was ever documented.
- Improved clarity around obtaining account IDs:. Using an <aside>. Is this correct?
- Found it odd that in code samples we refer to, for example, {ACCOUNT_ID} then in the docs we refer to that variable as @accountid@. I don't follow the inconsistency. Happy to change code examples to use accountId if preferred, but I don't see any merit in inconsistency in the same page.
- Adjusted headings, specifically differentiating between “Statistics response payload” and “Statistics response”, clarifying the API response structure. I don't think it was clear before what a statistics response payload was vs statistics metrics. I have made what I think is am improvement
- Improved metric definitions, clearly stating the inclusion of push notifications and integrations in outbound metrics. But also just made things a lot more concise.
- Simplified curl command examples, removing redundant --location, and I have no idea why `--request POST` flags was added for a GET method endpoint.
- 	Provided clearer context around API endpoints by explicitly linking to the correct documentation references.
[WEB-4296] fix: enforce remounting of inkeep search bar
Upgrade ably-ui 16.0.0 - new Meganav & Footer
Remove wording as such from docs
MongoDB LiveSync connector is not Beta
denissellu and others added 22 commits May 6, 2025 12:44
this will pull from ably change log
it is no longer being used
[WEB-4367] Fix column dimensions, default menu expansion behaviour
update chat-js and chat react versions to 0.6 (latest released)
Fixed issue where pub-sub-occupancy channel name is hard coded
Copy link

coderabbitai bot commented May 8, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

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.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@VeskeR VeskeR requested a review from m-hulbert May 8, 2025 14:04
@VeskeR VeskeR changed the base branch from main to integration/liveobjects May 8, 2025 14:04
@VeskeR VeskeR merged commit f50860a into integration/liveobjects May 8, 2025
6 checks passed
@VeskeR VeskeR deleted the liveobjects/merge-main-2025-05-08 branch May 8, 2025 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.