Skip to content

chore(main): release cdp-browser 0.4.0#8

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cdp-browser
Open

chore(main): release cdp-browser 0.4.0#8
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--cdp-browser

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.4.0 (2026-06-20)

Features

  • push: harden web push delivery reliability (t095) (#9) (d018f3c)

Bug Fixes

  • phone: keyboard-follow, safe-area, nav stack, pull-to-refresh (83e6397)
  • renderer: gate cmd shortcuts on physical key code, not character (#6) (5b512ff)

This PR was generated with Release Please. See documentation.

@dokploy-2026-03-01-6ei3s7

Copy link
Copy Markdown

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: github-actions[bot]
  • Repository: cdp-browser
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.


This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

1 similar comment
@dokploy-2026-03-01-6ei3s7

Copy link
Copy Markdown

🚨 Preview Deployment Blocked - Security Protection

Your pull request was blocked from triggering preview deployments

Why was this blocked?

  • User: github-actions[bot]
  • Repository: cdp-browser
  • Permission Level: none
  • Required Level: write, maintain, or admin

How to resolve this:

Option 1: Get Collaborator Access (Recommended)
Ask a repository maintainer to invite you as a collaborator with write permissions or higher.

Option 2: Request Permission Override
Ask a repository administrator to disable security validation for this specific application if appropriate.

For Repository Administrators:

To disable this security check (⚠️ not recommended for public repositories):
Enter to preview settings and disable the security check.


This security measure protects against malicious code execution in preview deployments. Only trusted collaborators should have the ability to trigger deployments.

🛡️ Learn more about this security feature

This protection prevents unauthorized users from:

  • Executing malicious code on the deployment server
  • Accessing environment variables and secrets
  • Potentially compromising the infrastructure

Preview deployments are powerful but require trust. Only users with repository write access can trigger them.

@github-actions github-actions Bot force-pushed the release-please--branches--main--components--cdp-browser branch from 61b7d85 to bcd7cbb Compare June 19, 2026 17:49
@github-actions github-actions Bot changed the title chore(main): release cdp-browser 0.3.1 chore(main): release cdp-browser 0.4.0 Jun 19, 2026
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--cdp-browser branch from bcd7cbb to c294e38 Compare June 19, 2026 18:29
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--cdp-browser branch from c294e38 to 51f104d Compare June 20, 2026 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants