Skip to content

Comments

release: v1.0.0-beta.36#6068

Merged
shulaoda merged 1 commit intomainfrom
release-v1.0.0-beta.36-1757333320
Sep 8, 2025
Merged

release: v1.0.0-beta.36#6068
shulaoda merged 1 commit intomainfrom
release-v1.0.0-beta.36-1757333320

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Sep 8, 2025

[1.0.0-beta.36] - 2025-09-08

Warning

💥 BREAKING CHANGES

🚀 Features

🐛 Bug Fixes

🚜 Refactor

🧪 Testing

⚙️ Miscellaneous Tasks

@graphite-app
Copy link
Contributor

graphite-app bot commented Sep 8, 2025

How to use the Graphite Merge Queue

Add the label graphite: merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

@netlify
Copy link

netlify bot commented Sep 8, 2025

Deploy Preview for rolldown-rs ready!

Name Link
🔨 Latest commit e5030c1
🔍 Latest deploy log https://app.netlify.com/projects/rolldown-rs/deploys/68bec75159c38300089c4eb7
😎 Deploy Preview https://deploy-preview-6068--rolldown-rs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Member

Merge activity

  • Sep 8, 12:11 PM UTC: The merge label 'graphite: merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

@shulaoda shulaoda merged commit 03b7b72 into main Sep 8, 2025
14 checks passed
@shulaoda shulaoda deleted the release-v1.0.0-beta.36-1757333320 branch September 8, 2025 12:13
graphite-app bot pushed a commit that referenced this pull request Sep 8, 2025
Move the breaking change block into `[!warning]`​  to make the block more noticeable.
see #6068 as an example
IWANABETHATGUY added a commit that referenced this pull request Sep 9, 2025
Move the breaking change block into `[!warning]`​  to make the block more noticeable.
see #6068 as an example
IWANABETHATGUY added a commit that referenced this pull request Sep 9, 2025
Move the breaking change block into `[!warning]`​  to make the block more noticeable.
see #6068 as an example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants