Repository navigation
chore(pkg): bump version to v1.1.1 #39
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,19 @@ | ||
| # Change Log | ||
|
|
||
| ## `v1.1.0` - 02/07/2026 | ||
| ## `v1.1.1` - 2026-07-13 | ||
|
|
||
| ### Fixed | ||
|
|
||
| - Normalize `git://` repository URLs for Discord links in `npm` command | ||
| - Optimize `run` command and expand its judge0 language alias map | ||
| - Harden `http` command against SSRF and DoS | ||
|
|
||
| ### Contributors | ||
|
|
||
| - [@calebephrem](https://github.com/calebephrem) | ||
| - [@gitcommit90](https://github.com/gitcommit90) | ||
|
|
||
| ## `v1.1.0` - 2026-07-02 | ||
|
|
||
| ### Added | ||
|
|
||
|
|
@@ -16,7 +29,7 @@ | |
| - Both the command and interaction handler now parse `CHANGELOG.md` dynamically | ||
| - Updated `profile` command to include a visual GitHub contribution activity graph in the embed response | ||
|
|
||
| ## `v1.0.0` - 01/07/2026 | ||
| ## `v1.0.0` - 2026-07-01 | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The v1.0.0 date conversion has the same issue as v1.1.1. The original Confidence: 5/5 Suggested FixIf the original date |
||
|
|
||
| ### Added | ||
|
|
||
|
|
@@ -28,3 +41,10 @@ | |
| - **Developer Utility Suite**: Introduced a robust collection of tools for code formatting, HTTP response parsing, regex testing, cryptographic ID generation, color validation, and metadata decoding. | ||
| - **Security Auditing**: Embedded a URL inspection utility to evaluate links for potential safety risks. | ||
| - **Community-Tier Access**: Implemented a server-membership verification system to seamlessly unlock premium commands for community supporters. | ||
|
|
||
| ### contributors | ||
|
|
||
| - [@calebephrem](https://github.com/calebephrem) | ||
| - [@joshdegr8](https://github.com/joshdegr8) | ||
| - [@louiszn](https://github.com/louiszn) | ||
| - [@skullvension](https://github.com/skullvension) | ||
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.
The date format conversion appears to have misinterpreted the original date. The original
02/07/2026(February 7, 2026 in MM/DD/YYYY format) is being converted to2026-07-13for v1.1.1, but the v1.1.0 date is being converted to2026-07-02(July 2, 2026). This creates a logical inconsistency where v1.1.1 is dated 11 days after v1.1.0, but the original dates suggest v1.1.0 was from February. The date format conversion needs to be verified against the actual release dates to ensure accuracy.Confidence: 5/5
Suggested Fix
Verify the correct release dates for v1.1.1 and v1.1.0. If the original dates were in MM/DD/YYYY format:
02/07/2026= February 7, 2026 → should be2026-02-0701/07/2026= January 7, 2026 → should be2026-01-07Please confirm the intended dates and update accordingly.