chore: cleanup unused contents

[JounQin]

Summary by CodeRabbit

• Chores
  • Added configuration files for Renovate and changeset management.
  • Updated GitHub Actions workflows to use the correct branch and adjusted build flags.
  • Removed an unused registry setting from the Yarn configuration.
• Documentation
  • Added a funding link to the project metadata.
• Refactor
  • Simplified the package metadata and configuration for the pyodide package.

[changeset-bot]

🦋 Changeset detected

Latest commit: 7e5f411

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@alauda/doom	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This update introduces configuration and metadata changes across multiple files. It adds new configuration files for changesets and Renovate, modifies GitHub Actions workflows for deployment and release, updates funding information in package.json, simplifies the pyodide/package.json, and removes an npm registry setting from .yarnrc.yml. No code or functional logic was altered.

Changes

File(s)	Change Summary
.changeset/five-geese-create.md	Added a changeset specifying a patch update for @alauda/doom to clean up unused contents.
.renovaterc	Added Renovate configuration extending from a remote preset.
.github/workflows/gh-pages.yml	Changed build command flag from -b doom to -p doom in the GitHub Pages deployment workflow.
.github/workflows/release.yml	Changed workflow trigger branch from "master" to "main" for release pipeline.
.yarnrc.yml	Removed the npmRegistryServer configuration pointing to https://registry.npmmirror.com.
package.json	Added a "funding" field with a URL to Open Collective.
pyodide/package.json	Simplified: removed dev dependencies, scripts, extra config, and replaced detailed metadata with concise fields. Updated ws dependency.

Poem

In the warren, configs hop and play,
Cleaning up the pyodide hay.
Funding links and workflows shift,
Renovate brings a tidy gift.
With flags and branches all aligned,
The codebase hums, well-defined!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5e69bcf and 7e5f411.

📒 Files selected for processing (7)

• .changeset/five-geese-create.md (1 hunks)
• .github/workflows/gh-pages.yml (1 hunks)
• .github/workflows/release.yml (1 hunks)
• .renovaterc (1 hunks)
• .yarnrc.yml (0 hunks)
• package.json (1 hunks)
• pyodide/package.json (2 hunks)

💤 Files with no reviewable changes (1)

• .yarnrc.yml

🔇 Additional comments (7)

.renovaterc (1)

1-5: Renovate configuration is valid.
The new .renovaterc correctly extends the shared preset and introduces no custom overrides, aligning with the repository’s housekeeping goals.

.github/workflows/release.yml (1)

6-6: Ensure consistency of branch naming.
You’ve updated the trigger branch to main. Please verify that all other workflows, documentation, and any deployment scripts have been updated accordingly to avoid residual references to master.

package.json (1)

8-8: Add funding field.
The new "funding" field correctly provides a sponsorship link according to the npm spec and will surface the Open Collective URL in registry listings.

pyodide/package.json (2)

9-10: Simplified repository and homepage fields.
Converting the repository metadata to a string and updating the homepage to include #readme is a clean simplification of the file.

---

53-53: Upgrade ws dependency.
Bumping ws to ^8.18.2 likely addresses known vulnerabilities. Please confirm that this version upgrade does not introduce breaking changes in consumers of the package.

.changeset/five-geese-create.md (1)

1-6: Valid Changeset entry.
The new patch changeset for @alauda/doom correctly documents the housekeeping chore and will trigger a patch release.

.github/workflows/gh-pages.yml (1)

31-33:

Details

❓ Verification inconclusive

Confirm build command correctness after flag change

The build step now uses yarn doom build -p doom instead of the previous -b flag. Please verify that the -p flag produces the intended build artifacts and update any other CI scripts or documentation that refer to doom build -b doom to maintain consistency across the codebase.

To verify locally, you can run:

And to find lingering references:

---

🏁 Script executed:

yarn doom build -p doom && ls dist

Length of output: 244

---

🏁 Script executed:

rg -n "doom build -b" .

Length of output: 25

---

File: .github/workflows/gh-pages.yml
Lines: 31–33

      - name: Build the project
        run: yarn doom build -p doom

Confirm build command correctness after flag change

We attempted to verify yarn doom build -p doom in the CI sandbox but couldn’t validate the output artifacts due to missing dependencies. A search for any remaining doom build -b references in the codebase returned no matches. Please:

• Run locally:

  yarn doom build -p doom && ls dist

  to confirm the -p flag produces the expected build artifacts.
• Review CI scripts, documentation, and templates for any outdated -b flag references and update them if found.

---

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

Support

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

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

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

Documentation and Community

• 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.

[Copilot]

Pull Request Overview

This PR focuses on cleaning up unused contents from the repository configuration files. Key changes include:

• Removal of outdated and unused metadata and script sections from pyodide/package.json.
• Updates to the .yarnrc.yml configuration by removing an unnecessary registry configuration.
• Addition of a new .renovaterc file and an update to the gh-pages workflow build command.

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
pyodide/package.json	Removed extra metadata, devDependencies, and scripts.
.yarnrc.yml	Removed redundant npm registry server entry.
.renovaterc	Introduced new configuration for Renovate.
.github/workflows/gh-pages.yml	Updated the build command flag from -b to -p for doom.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/alauda/Doom/@alauda/doom@3

commit: 7e5f411