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

Release v3.0 #480

Merged
merged 2 commits into from
Nov 28, 2024
Merged

Release v3.0 #480

merged 2 commits into from
Nov 28, 2024

Conversation

zds-s
Copy link
Member

@zds-s zds-s commented Nov 28, 2024

Summary by CodeRabbit

  • Chores
    • Updated the .gitignore file to include *.lock and storage/swagger/http.json.
    • Added a new dependency, "friendsofhyperf/tinker": "^3.1", in composer.json.
    • Updated dependency versions in composer.json from "3.0-RC" to "3.0" for various mineadmin packages.
    • Removed the storage/swagger/http.json file, which contained the OpenAPI specification for the API.

@dosubot dosubot bot added the size:S This PR changes 10-29 lines, ignoring generated files. label Nov 28, 2024
Copy link

coderabbitai bot commented Nov 28, 2024

Walkthrough

The changes in this pull request involve modifications to three files: .gitignore, composer.json, and storage/swagger/http.json. The .gitignore file has been updated to include two entries, *.lock and storage/swagger/http.json, with the latter being a new addition. The composer.json file has seen updates to the version constraints for several mineadmin packages, changing them from "3.0-RC" to "3.0". Lastly, the file storage/swagger/http.json, which contained an OpenAPI specification, has been deleted.

Changes

File Change Summary
.gitignore Added entries: *.lock, storage/swagger/http.json
composer.json Added new dependency: "friendsofhyperf/tinker": "^3.1"; updated version constraints from "3.0-RC" to "3.0" for multiple mineadmin dependencies: access, app-store, auth-jwt, core, jwt, support, swagger, upload
storage/swagger/http.json File deleted

Poem

In the garden where code does play,
New rules for ignoring, hip-hip-hooray!
Versions updated, clear as the day,
A spec now gone, but we’ll find our way.
With each little change, we hop and sway! 🐰✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 88c2919 and ed96e44.

📒 Files selected for processing (1)
  • composer.json (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • composer.json

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

Copy link

@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 and nitpick comments (1)
composer.json (1)

58-65: Consider documenting upgrade steps for consumers.

Since this is a major release moving from RC to stable, consider documenting any breaking changes or upgrade steps required for consumers of these packages.

Would you like me to help create an upgrade guide or release notes document?

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 666fd46 and 88c2919.

📒 Files selected for processing (3)
  • .gitignore (1 hunks)
  • composer.json (1 hunks)
  • storage/swagger/http.json (0 hunks)
💤 Files with no reviewable changes (1)
  • storage/swagger/http.json
✅ Files skipped from review due to trivial changes (1)
  • .gitignore
🔇 Additional comments (2)
composer.json (2)

58-65: Version constraints updated consistently for release.

All mineadmin package versions have been consistently updated from "3.0-RC" to "3.0", which aligns with the release objectives.

Let's verify there are no remaining RC references in the codebase:

✅ Verification successful

Version upgrade to 3.0 verified successfully

The codebase has been thoroughly checked and all mineadmin package versions have been consistently updated to "3.0". No remaining references to "3.0-RC" were found. The only other version references found are for php-cs-fixer (^3.0) and a development branch alias (3.0-dev), which are both correct and unrelated to the RC upgrade.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any remaining RC version references
# Expected: No occurrences of "3.0-RC" should be found

rg -i "3\.0-RC" --type-add 'config:*.{json,yaml,yml,php}' -t config

Length of output: 69


Script:

#!/bin/bash
# Let's try a broader search for any RC references in all files
rg -i "3\.0-rc"

# Also search for version-related patterns in composer files
rg -i "version|3\.0" composer.*

Length of output: 383


58-65: Verify API documentation availability after swagger file removal.

The removal of storage/swagger/http.json could impact API documentation. Since the project depends on zircote/swagger-php, ensure that:

  1. The OpenAPI specification can still be generated
  2. API documentation remains accessible to consumers

Let's check for alternative swagger configuration or documentation:

✅ Verification successful

API documentation generation is properly configured and functional

The swagger configuration is intact and well-configured:

  • Auto-generation is enabled (auto_generate => true)
  • Documentation is scanned from /app/Http and /app/Schema directories
  • OpenAPI 3.0 specifications are defined in Server.php
  • The removed storage/swagger/http.json file is auto-generated in the configured output directory (json_dir => BASE_PATH . '/storage/swagger')
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Look for swagger/OpenAPI related files
# Expected: Find alternative swagger configuration or documentation files

# Search for swagger config files
fd -e php -e yaml -e json . | rg -i "swagger|openapi"

# Search for swagger annotations in code
rg -l "@OA|@OpenAPI" -t php

Length of output: 148


Script:

#!/bin/bash
# Let's examine the swagger configuration and server files
cat config/autoload/swagger.php
echo "---"
cat app/Http/Common/Swagger/Server.php

# Let's also check for any API controller files that might contain swagger annotations
fd -e php . | rg -i "controller" | xargs rg -l "@OA|@SWG|@Swagger"

Length of output: 2299

@zds-s zds-s merged commit 17acd9b into master Nov 28, 2024
34 checks passed
@zds-s zds-s deleted the release-v3.0 branch November 28, 2024 11:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Composer size:S This PR changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant