Skip to content

Prepare 1.1.0 - #5

Merged
mmcky merged 1 commit into
mainfrom
release-1.1.0
Aug 3, 2026
Merged

Prepare 1.1.0#5
mmcky merged 1 commit into
mainfrom
release-1.1.0

Conversation

@mmcky

@mmcky mmcky commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Release chore ahead of tagging v1.1.0.

Moves the [Unreleased] entries — everything from #3 and #4 — under a dated [1.1.0] heading, and leaves a fresh [Unreleased] section above it. Nothing else in the repo carries a version string, so this is the only bump.

It also drops the "GitHub Marketplace listing" bullet from the [1.0.0] section. That listing does not exist: Marketplace requires a published GitHub Release, and gh release list on this repository is empty. In its place is a short note recording what is actually true of that tag — v1.0.0 points at 890d35e, the repository's initial commit, which predates the test suite, the CI workflow and the README fixes.

The tag is deliberately left where it is. Moving a tag someone may have pinned is worse than leaving a bad one in place, and the note tells readers to pin v1 or v1.1.0 instead.

After this merges

  • Tag v1.1.0 at the merge commit
  • Create the moving v1 tag at the same commit, which is what makes the 17 uses: references across the README and examples.md resolve for the first time
  • Publish a GitHub Release for v1.1.0 with notes drawn from this changelog

No Marketplace publication, per the decision to keep this release to tags plus a GitHub Release.

Moves the Unreleased entries under a dated 1.1.0 heading and leaves a
fresh Unreleased section above it.

Also drops the "GitHub Marketplace listing" bullet from 1.0.0. No
GitHub Release has ever been published for this repository, and
Marketplace requires one, so the listing does not exist. Records what
is actually true of that tag instead: v1.0.0 points at the initial
commit, which predates the test suite, the CI workflow and the README
fixes. It is left where it is rather than moved, since moving a tag
somebody may have pinned is worse than leaving a bad one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings August 3, 2026 06:12
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown

🔗 Link Check Results

🚨 1 broken link(s) and 3 redirect(s) were found.

Build Details:


Link Check Summary

  • Total broken links: 1
  • Total redirects found: 3

Broken Links

tests/broken-links.html - 1 broken link(s):
https://this-host-cannot-resolve.invalid - Status: 0 (Connection Error)
Link text: Broken domain

tests/broken-links.html - 3 redirect(s):
🔄 http://github.com/QuantEcon/meta -> https://github.com/QuantEcon/meta (1 redirects)
🔄 https://github.com/QuantEcon/meta/blob/master/README.md -> https://github.com/QuantEcon/meta/blob/main/README.md (1 redirects)
🔄 http://docs.python.org/2.7/library/urllib.html -> https://docs.python.org/2.7/library/urllib.html (1 redirects)

AI-Powered Suggestions

tests/broken-links.html - AI Suggestions:
🤖 http://github.com/QuantEcon/meta
Issue: Redirected 1 times
💡 redirect_update: https://github.com/QuantEcon/meta
Reason: Update to final destination to avoid 1 redirect(s)
🤖 https://github.com/QuantEcon/meta/blob/master/README.md
Issue: Redirected 1 times
💡 redirect_update: https://github.com/QuantEcon/meta/blob/main/README.md
Reason: Update to final destination to avoid 1 redirect(s)
🤖 http://docs.python.org/2.7/library/urllib.html
Issue: Redirected 1 times
💡 redirect_update: https://docs.python.org/2.7/library/urllib.html
Reason: Update to final destination to avoid 1 redirect(s)


Next Steps:

  1. Review the broken links listed above
  2. Update or remove broken links
  3. Consider applying AI suggestions for better alternatives
  4. Push the changes to update this PR

📝 This comment was automatically generated by the AI-Powered Link Checker Action.

@mmcky
mmcky merged commit 39255b1 into main Aug 3, 2026
5 checks passed

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟢 Ready to approve

The change is confined to CHANGELOG.md and the edits are consistent with the PR description without introducing code or behavioral risk.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

Release-prep chore for v1.1.0 by updating the changelog to reflect the new release and correct a previously inaccurate claim about v1.0.0.

Changes:

  • Move the existing changelog entries from [Unreleased] into a dated [1.1.0] - 2026-08-03 section, leaving an empty [Unreleased] section at the top.
  • Remove the incorrect “GitHub Marketplace listing” bullet from [1.0.0] and replace it with an explanatory note about what the v1.0.0 tag actually points to.
File summaries
File Description
CHANGELOG.md Adds the 1.1.0 release heading/date and corrects the 1.0.0 section’s Marketplace/tag narrative.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

@mmcky
mmcky deleted the release-1.1.0 branch August 3, 2026 09:54
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.

2 participants