-
Notifications
You must be signed in to change notification settings - Fork 12
Release 1.2.0 #317
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
Open
prateek-kumar-improving
wants to merge
3
commits into
main
Choose a base branch
from
release-1.2
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Release 1.2.0 #317
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 8111
🌐 Web query:
PEAR PECL versioning solution2 1.2.0RC1 1.2.0-rc1 canonical version handling💡 Result:
In the context of the PHP Extension Community Library (PECL) and PEAR versioning standards, the canonical way to handle Release Candidate (RC) versions is to append the string "RC" followed by an integer directly to the version number, such as 1.2.0RC1 [1][2][3]. The format "1.2.0-rc1" is not considered canonical and is generally not recognized by the PEAR installer, which does not handle hyphens in package version strings [4]. The "Solution2" referred to in your query is a specific RFC (Request for Comments) titled "peclversioning/solution2" [5][6]. This proposal sought to address the historically anarchic nature of PECL versioning by establishing a standardized naming convention and maturity state system [6][7]. According to this standard: - Version numbers should be numeric strings (e.g., 1.2.0) [8]. - RC states are achieved by using the "beta" stability state in the package.xml file and appending "RC" followed by an integer (e.g., 1.2.0RC1) to the version number [3][5]. - Using this format ensures that the versioning is compatible with PHP's version_compare function and the PEAR installer's expectations [8][4]. The "Solution2" RFC emphasizes that this approach provides a clear path for maturity, moving from development/alpha/beta states toward stable releases [5]. Developers are encouraged to use this consistent structure to allow users to easily identify the maturity and compatibility status of extensions [6].
Citations:
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 41803
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 389
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 50385
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 428
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 470
🏁 Script executed:
Repository: valkey-io/valkey-glide-php
Length of output: 13126
Use PEAR/PECL release-candidate syntax consistently. Set
VALKEY_GLIDE_PHP_VERSIONand<release>to1.2.0RC1, retain beta stability, and update the-rcNchecks in.github/workflows/publish-pecl.ymland.github/workflows/validate-version/action.yml; otherwise the release workflow rejects the canonical version and runs the wrong package validation.📍 Affects 2 files
common.h#L14-L14(this comment)package.xml#L18-L23🤖 Prompt for AI Agents