## Problem solved
https://linear.app/thirdweb/issue/BLOCK-412/add-api-key-scope
Added Nebula service scope to the service definitions and included it in the hidden services list.
<!-- start pr-codex -->
---
## PR-Codex overview
This PR introduces the `nebula` service scope to the project and updates the related configurations and validations accordingly. It also modifies the pull request body check to include the `BLOCK` keyword.
### Detailed summary
- Added `nebula` service scope in `packages/service-utils/src/core/services.ts` with properties: `name`, `title`, and `description`.
- Updated `HIDDEN_SERVICES` in `apps/dashboard/src/components/settings/ApiKeys/validations.ts` to include `nebula`.
- Modified the pull request body check in `.github/workflows/linear.yml` to include `BLOCK`.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
---
## PR-Codex overview
This PR adds a GitHub Actions workflow to automatically close stale issues and pull requests after a specified period of inactivity.
### Detailed summary
- Introduced a new workflow in `.github/workflows/stale.yml` named 'Close stale issues and PRs'.
- Configured the workflow to trigger on a schedule using a cron job.
- Set the job to run on `ubuntu-latest`.
- Utilized `actions/stale@v9` for managing stale issues and PRs.
- Configured messages for stale issues and PRs.
- Defined `days-before-stale` as 30 and `days-before-close` as 5.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR introduces a new workflow in the `.github/workflows/linear.yml` file that ensures pull requests contain a linked issue in their body.
### Detailed summary
- Added a new workflow named `Check for linked issue in pull request body`.
- Configured the workflow to trigger on `pull_request` events.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
## Problem solved
Fixes https://linear.app/thirdweb/issue/ENG-2/better-enforce-linear-use
<!-- start pr-codex -->
---
## PR-Codex overview
This PR introduces a GitHub Actions workflow to check the pull request body for specific keywords ("CNCT" or "DASH"). If these keywords are found, it confirms a linked issue; otherwise, it fails the check.
### Detailed summary
- Added a workflow named `Check for "linear" in pull request body` in `.github/workflows/linear.yml`.
- Configured the workflow to trigger on `pull_request` events (opened and edited).
- Implemented a job `check_linear_in_pr_body` to verify the presence of keywords in the PR body.
- Utilized `curl` to fetch the PR body and `grep` to search for keywords.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
tl;dr: https://graphite.dev/docs/stacking-and-ci#reducing-ci-runs-for-github-actions
<!-- start pr-codex -->
---
## PR-Codex overview
This PR optimizes the CI workflow by adding a step to skip unnecessary processes based on a condition.
### Detailed summary
- Added `optimize_ci` job with skip condition
- Updated `build`, `lint`, `test`, `e2e`, and `size` jobs to depend on `optimize_ci` and skip if condition is met
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
### TL;DR
This PR adjusts the `.changeset/config.json` to update dependency settings and reorganizes changeset markdown files under a new directory.
### What changed?
- Removed `fixed` and `linked` fields from the `.changeset/config.json`.
- Updated the `ignore` array in `config.json` to include additional thirdweb-dev packages.
- Moved existing `.changeset/*.md` files to a newly created `v4-changesets-apply-later` directory.
### How to test?
Verify that dependency updates and changeset file reorganization are reflected correctly in the `.changeset/config.json` and file structure.
### Why make this change?
We are temporarily only releasing v5 packages (while figuring a path forward regarding `@thirdweb-dev/react` with npm).
---
### TL;DR
This pull request updates the CI configuration and removes the merge group workflow triggers.
### What changed?
- Added new CI configuration file `.github/workflows/CI.yml` with enhanced jobs for building, linting, testing, and benchmarking.
- Removed merge group workflow triggers from the legacy CI file `.github/workflows/CI_legacy.yml`.
### How to test?
- Verify that the new CI workflow runs successfully on push and pull request events.
- Ensure all jobs (build, lint, test, e2e, benchmark, size) complete without errors.
- Check that merge group workflow triggers are no longer present in the legacy CI configuration.
### Why make this change?
This change aims to improve the CI process by adding more comprehensive job steps, including concurrency control and better separation of tasks. Removing the merge group triggers from the legacy CI helps to declutter and refine the workflow definitions.
---
<!-- start pr-codex -->
---
## PR-Codex overview
This PR updates the GitHub Actions workflow to enhance CI with new jobs, tests, and environment variables.
### Detailed summary
- Replaced legacy CI workflow with a new comprehensive CI workflow
- Added jobs for linting, testing, E2E testing, benchmarks, and bundle size reporting
- Updated triggers for push, pull requests, and workflow dispatch
- Added concurrency settings and environment variables
- Enhanced E2E testing with multiple package managers and bundlers
- Improved code coverage reporting with Codecov
- Enabled remote caching for faster workflows
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
<!-- start pr-codex -->
## PR-Codex overview
This PR updates Yarn installation and package versions, enhances test project scripts, and modifies Turbo tasks configuration.
### Detailed summary
- Updated Yarn installation to version 1.22.19
- Updated package versions in the test project
- Modified Turbo tasks configuration for various packages and builds
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->