docs: move upcoming changes to released section (23 Aug 2026) - #1353
Merged
Conversation
Every version in the "Upcoming release" block was already tagged and published to PyPI on 23 Aug 2026, so the section was stale. Moves the section headers, leaving the entries themselves untouched. Released in this wave: rpaframework 33.0.1, rpaframework-core 13.0.3, rpaframework-pdf 11.0.2, rpaframework-recognition 8.0.2, rpaframework-google 12.0.1, rpaframework-sema4ai 1.1.1. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The "Upcoming release" block in
docs/source/releasenotes.rstwas stale: every version listed in it had already been tagged and published to PyPI on 23 Aug 2026. This rolls it into theReleasedsection under a23 Aug 2026heading.Released in that wave:
rpaframeworkrpaframework-corerpaframework-pdfrpaframework-recognitionrpaframework-googlerpaframework-sema4aiApproach
Follows the same pattern as the last rollover (
794c4bf50, 29 Jun 2026): the section headers move rather than the content block, so the diff is+8/-3and the entries themselves are provably untouched.docs/source/packages.rstneeds no change — its "Latest versions" badges are shields.io images that read from PyPI directly.Verification
Parsed the file with
docutilsbefore and after and compared, normalising for the 5-line offset the insertion introduces:(Those 12 are pre-existing warnings elsewhere in this long file, unrelated to this change.)
Also checked every date heading's underline length against its title: all 32 correct, including the new
23 Aug 2026.One thing worth a second look — not changed here
The first entry credits the
RPA.Desktop.Windowsremoval withfixes :issue:1322``, and #1343's commit message says the same. But #1322 is titled "RPA.Desktop Wait for Element does not wait for element" — a timeout bug — and #1343 only deletedRPA.Desktop.Windows.wait_for_element. `RPA.Desktop`'s own `wait_for_element` in `packages/main/src/RPA/Desktop/keywords/finder.py` was left untouched.So either the issue was closed by removal while the reporter's actual
RPA.Desktopcomplaint still stands, or the reference is a slip. Left exactly as-is — this PR is a pure move and that call is yours. The published release note on the docs site (robocorp/documentation#1182) omits the #1322 link rather than surfacing a confusing reference to readers.🤖 Generated with Claude Code