Skip to content

chore: prepare for release v2.3.1 #1326

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 26, 2025
Merged

chore: prepare for release v2.3.1 #1326

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

6 changes: 3 additions & 3 deletions Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "parseable"
version = "2.3.0"
version = "2.3.1"
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Verification agent

❓ Verification inconclusive

Confirm version bump and release notes alignment
The version field was updated from "2.3.0" to "2.3.1". Ensure that your CHANGELOG.md (or equivalent) includes an entry for v2.3.1 and that CI/CD workflows will tag and publish the correct release.

Run the following to verify the changelog contains the new version header:

🏁 Script executed:

#!/bin/bash
# Verify that CHANGELOG.md includes a 2.3.1 entry
grep -R "^## \[2\.3\.1\]" CHANGELOG.md

Length of output: 86

🏁 Script executed:

#!/bin/bash
# Locate any changelog or release notes file in the repository
find . -type f -iname "*changelog*"

Length of output: 37

Add or update release notes for v2.3.1
I didn’t find a CHANGELOG.md (or any other release-notes file) in the repo to record the v2.3.1 bump. Please add or update your changelog/release notes with an entry for v2.3.1 and ensure your CI/CD pipeline will pick it up when tagging and publishing the release.

• Create or update CHANGELOG.md (or your chosen file) with:

## [2.3.1] – YYYY-MM-DD
- <!-- summary of changes in this release -->

• Verify CI/CD workflows reference this file for tagging/publishing.

🤖 Prompt for AI Agents 
In Cargo.toml at line 3, the version was updated to 2.3.1 but there is no
corresponding entry in the changelog or release notes. Create or update a
CHANGELOG.md file with a new section for version 2.3.1 including the release
date and a summary of changes. Also, verify that your CI/CD pipeline references
this changelog file to correctly tag and publish the release.

authors = ["Parseable Team <[email protected]>"]
edition = "2021"
rust-version = "1.83.0"
Expand Down Expand Up @@ -139,8 +139,8 @@ arrow = "54.0.0"
temp-dir = "0.1.14"

[package.metadata.parseable_ui]
assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.0/build.zip"
assets-sha1 = "52e91ff6accc6717110e20b9d00f0c678d36a011"
assets-url = "https://parseable-prism-build.s3.us-east-2.amazonaws.com/v2.3.1/build.zip"
assets-sha1 = "2d420243ae85b730b201ab1c15b44fae57af992b"

[features]
debug = []
Expand Down
Loading