Repository navigation
code-modernization: look up whether target versions are supported - #7170
Closed
claude[bot] wants to merge 1 commit into
Closed
claude[bot] wants to merge 1 commit into
claude[bot] wants to merge 1 commit into
Conversation
…ore proposing it Commands proposed language and framework versions from the model's memory, which is older than today, so a plan could name a release that is already out of support. A shared rule (references/target-versions.md) now has each command look versions up, record them in a Target versions table with the support end date and source, keep a version the person chose with a warning, and mark a version that could not be checked as unverified instead of guessing. Version 1.1.0.
Contributor
|
Thanks for your interest! Plugins are now submitted at https://claude.ai/directory/manage. Plugins accepted there are served across Claude products. The Pull requests here are not monitored, so please use the link above to submit or update a plugin. This pull request has been closed automatically, because this repository only takes changes from Anthropic team members. |
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
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.
Before: Commands that propose a target took version numbers from the model's memory, which is older than today. On a toy AngularJS 1.5 / Java 7 / Spring 4 app,
reimaginedrafted "Angular 18, Spring Boot 3.3" in one run and "Spring Boot 3 / Java 21" in another, with no lookup.After: Versions are looked up and shown in a Target versions table: support end, source, date checked, status. The same app now gets Angular 22, Java 25 LTS and Spring Boot 4.1. A version you named is kept, with a warning and a supported alternative if its support has ended. If every lookup fails, the row says
unverified, with no remembered number, and a person pins it before the build.How: One shared rule,
references/target-versions.md. Each command that proposes, confirms or builds for a version carries a short summary and points to it.architecture-criticgets no web tools on purpose: it judges the recorded table. Version 1.1.0.Test
reimagine, stopped at the architecture checkpoint: dated, sourced table from web search.reimaginewith lookups denied: every rowunverified, and it carried on.reimaginewith Angular 19 named: kept, and flagged as out of support since 2026-05-19.briefwith .NET 8: kept, and raised as an open question. Not asked again onceINTENT.mdrecorded the decision.reimaginecase only.Not tested: opening endoflife.date or vendor pages (unreachable from the test machine), default and accept-edits permission modes, scaffolding on the new table, and live
transform,uplift,preflightorassessruns. Dates taken from search snippets can be wrong (one run had a wrong Angular 22 end date), so each row names its source.Generated by Claude Code