Add no follow

[reddy-vishwanath]

https://github.com/quintype/page-builder/issues/4024

Summary by CodeRabbit

• Chores
  • Bumped application version to 7.34.5-add-no-follow.0.
  • Updated underlying AMP integration dependency to the latest patch release for improved compatibility and maintenance.
  • General maintenance updates with no changes to public APIs.
  • No user-facing functionality changes expected; stability and consistency improvements only.
  • Prepares the codebase for future incremental updates without altering existing behavior.

[coderabbitai]

Walkthrough

In package.json, the project version is incremented and the @quintype/amp dependency is updated to a new prerelease range.

Changes

Cohort / File(s)	Summary
Version and dependency bump package.json	Update version 7.34.4 → 7.34.5-add-no-follow.0; bump dependency @quintype/amp ^2.22.0 → ^2.22.1-add-no-follow.1

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: amp hero image for migrated stories #465 — Also updates package.json to bump the @quintype/amp dependency (different target versions).

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch add-no-follow

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbit in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbit 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:
  • @coderabbit gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbit read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbit help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbit ignore or @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbit summary or @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbit or @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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

3-3: Lock prerelease publishes to the “beta” tag
Add the following to package.json so that npm publish defaults to your prerelease tag instead of overwriting latest:

{
  "publishConfig": { "tag": "beta" }
}

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 05a08d9 and 95a1d68.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (2 hunks)

🔇 Additional comments (1)

package.json (1)

36-36: Pin the prerelease exactly and update lockfile
Remove the caret so npm won’t float to newer prereleases:

-    "@quintype/amp": "^2.22.1-add-no-follow.1",
+    "@quintype/amp": "2.22.1-add-no-follow.1",

Manually verify that this range no longer matches newer prereleases and that stable 2.22.1 isn’t selected, then regenerate and commit your lockfile to prevent CI drift.