Merge main into integration/liveobjects
#2542
Open
Conversation
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
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.
[WEB-4277] Update Inkeep to cxkit 0.5.36
…ext-15.2.3 chore(deps): bump next from 15.1.7 to 15.2.3 in /examples
…o avoid processing
[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.
Update Stats docs
[WEB-4296] fix: enforce remounting of inkeep search bar
Upgrade ably-ui 16.0.0 - new Meganav & Footer
…butors Add contributing guide for examples
[WEB-4086] Port Next projects to Vite 4
Remove wording as such from docs
MongoDB LiveSync connector is not Beta
… REST API section.
The X-Ably-Version header was redundant and not strictly required.
Removing envelope param, this can be governed by content type. Adding moderation failure response.
Added per-response error examples. Added supported content-types. Some small changes in wording for clarity.
Updated the production server URL to "https://main.realtime.ably.net/".
Chat: Adding rest api documentation to chat
Adds the product to the "about" page so it appears on the tab, as it currently says PubSub
chat: add product to about page
Fix: remove old homepage.yaml
No longer need to weirdly `await` things, brings us more in line with other platforms. Resolves ably/ably-chat-swift#254.
…chat-swift-MainActor [ECO-5283] Update Swift chat docs for `@MainActor` changes
[WEB-4317] Bump ably-ui to 16.1.0 and update button/menu class names
chore: bump ably-ui to 16.1.1, update outdated lh var usage
The meta tag is populated from the website proxy. When it's present, open the Hubspot chat. Hubspot will be configured to only open if agents are online, which is why no additional status checks are needed.
[WEB-4261] Open Hubspot chat when conversation Meta tag is present
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Merges
mainintointegration/liveobjectsbranch to prepare for the liveobjects docs release in #2541.There were no conflicts to resolve during the merge.
Checklist