Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update code to support @octokit/request v9 and @octokit/graphql v8 #3697

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

AritraDey-Dev
Copy link

@AritraDey-Dev AritraDey-Dev commented Feb 17, 2025

fixes #3690
Description
Update package.json to support @octokit/request v9.2.2 and @octokit/graphql v8.2.1.

  • Update @octokit/graphql to version 8.2.1.
  • Add @octokit/request with version 9.2.2.

Summary by CodeRabbit

  • Chores
    • Enhanced key underlying technology components for increased stability and reliability. These updates include upgraded dependencies and the addition of new packages, ensuring a robust foundation for continued performance and future improvements while maintaining a seamless experience for users.
    • Updated the project to require Node.js version >=16 and npm version ^8.0.0.

Copy link
Contributor

coderabbitai bot commented Feb 17, 2025

Warning

Rate limit exceeded

@AritraDey-Dev has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 20 minutes and 7 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between c7fea4e and e6bf4d4.

📒 Files selected for processing (2)
  • package.json (1 hunks)
  • tests/dashboard/build-dashboard.test.js (3 hunks)

Walkthrough

The pull request updates the package.json file by modifying the dependencies. The version of @octokit/graphql is upgraded from ^7.0.2 to ^8.2.1, and new dependencies @octokit/request (^9.2.2), @octokit/types (^13.8.0), and fast-content-type-parse (^2.0.1) are added. Additionally, a new "engines" section is introduced, specifying the required Node.js version as >=16 and npm version as ^8.0.0. A trailing comma has been added after the existing yaml dependency for formatting consistency.

Changes

File Change Summary
package.json Updated dependency @octokit/graphql from ^7.0.2 to ^8.2.1; added dependencies @octokit/request (^9.2.2), @octokit/types (^13.8.0), and fast-content-type-parse (^2.0.1); added "engines" section specifying Node.js >=16 and npm ^8.0.0; added trailing comma after yaml.
scripts/dashboard/build-dashboard.js Transitioned from CommonJS to ES module syntax by replacing require with import statements and updated export statement from module.exports to export.

Possibly related PRs

Suggested labels

do-not-merge, autoupdate

Suggested reviewers

  • derberg
  • devilkiller-ag
  • akshatnema
  • sambhavgupta0705
  • anshgoyalevil
  • asyncapi-bot-eve
  • Mayaleeeee

Poem

Hoppity, hoppity, I'm a coding rabbit,
Skipping through dependencies with a joyful habit.
Upgraded versions and new friends join the spree,
Bringing fresh breezes to our repository.
With ASCII hops and a twitch of my nose,
I celebrate these changes from my burrow of code!


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 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.

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. (Beta)
  • @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.

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.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Copy link

netlify bot commented Feb 17, 2025

Deploy Preview for asyncapi-website ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit e6bf4d4
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67bd7d792c365c0008a0f1b1
😎 Deploy Preview https://deploy-preview-3697--asyncapi-website.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 site configuration.

@AritraDey-Dev AritraDey-Dev changed the title fix: Update code to support @octokit/request v9 and @octokit/graphql v8 fix: update code to support @octokit/request v9 and @octokit/graphql v8 Feb 17, 2025
@anshgoyalevil
Copy link
Member

anshgoyalevil commented Feb 23, 2025

@AritraDey-Dev Make sure all the tests and build pass

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🔭 Outside diff range comments (1)
scripts/dashboard/build-dashboard.js (1)

180-180: ⚠️ Potential issue

Update the module execution check for ES modules

The require.main === module check is specific to CommonJS and won't work in an ES module environment. This line needs to be updated to the ES module equivalent.

- if (require.main === module) {
+ if (import.meta.url === `file://${process.argv[1]}`) {
🧹 Nitpick comments (1)
scripts/dashboard/build-dashboard.js (1)

184-184: Successfully migrated to ES module exports

The export statement has been correctly migrated from CommonJS module.exports to ES module export.

For better readability, consider formatting the exports with each name on a separate line as suggested by the linter:

- export { getLabel, monthsSince, mapGoodFirstIssues, getHotDiscussions, getDiscussionByID, getDiscussions, writeToFile, start, processHotDiscussions, pause };
+ export {
+   getLabel,
+   monthsSince,
+   mapGoodFirstIssues,
+   getHotDiscussions,
+   getDiscussionByID,
+   getDiscussions,
+   writeToFile,
+   start,
+   processHotDiscussions,
+   pause
+ };
🧰 Tools
🪛 ESLint

[error] 184-184: Replace ·getLabel,·monthsSince,·mapGoodFirstIssues,·getHotDiscussions,·getDiscussionByID,·getDiscussions,·writeToFile,·start,·processHotDiscussions,·pause· with ⏎··getLabel,⏎··monthsSince,⏎··mapGoodFirstIssues,⏎··getHotDiscussions,⏎··getDiscussionByID,⏎··getDiscussions,⏎··writeToFile,⏎··start,⏎··processHotDiscussions,⏎··pause⏎

(prettier/prettier)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2cad54c and c7fea4e.

📒 Files selected for processing (1)
  • scripts/dashboard/build-dashboard.js (2 hunks)
🧰 Additional context used
🪛 ESLint
scripts/dashboard/build-dashboard.js

[error] 4-4: Unexpected use of file extension "js" for "./issue-queries.js"

(import/extensions)


[error] 184-184: Replace ·getLabel,·monthsSince,·mapGoodFirstIssues,·getHotDiscussions,·getDiscussionByID,·getDiscussions,·writeToFile,·start,·processHotDiscussions,·pause· with ⏎··getLabel,⏎··monthsSince,⏎··mapGoodFirstIssues,⏎··getHotDiscussions,⏎··getDiscussionByID,⏎··getDiscussions,⏎··writeToFile,⏎··start,⏎··processHotDiscussions,⏎··pause⏎

(prettier/prettier)

🔇 Additional comments (1)
scripts/dashboard/build-dashboard.js (1)

1-4: Successfully migrated to ES module imports

The imports have been properly migrated from CommonJS require statements to ES module import statements, which aligns with the PR objective to update Octokit dependencies.

Note: The ESLint warning about file extensions is a configuration issue. Including .js extensions in imports is actually required for ES modules in Node.js environments.

🧰 Tools
🪛 ESLint

[error] 4-4: Unexpected use of file extension "js" for "./issue-queries.js"

(import/extensions)

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.

fix: Update code to support @octokit/request v9 and @octokit/graphql v8
2 participants