Skip to content

fix: Add LTS 2026 feed URLs. - #302

Open
shichen85 wants to merge 1 commit into
developfrom
fix/lts_2026
Open

fix: Add LTS 2026 feed URLs.#302
shichen85 wants to merge 1 commit into
developfrom
fix/lts_2026

Conversation

@shichen85

Copy link
Copy Markdown
Member

No description provided.

@shichen85
shichen85 requested a review from adam-coster as a code owner June 10, 2026 17:02
@adam-coster

Copy link
Copy Markdown
Member

There are probably lots of other places in the code that do stuff depending on which channel is being used -- did you already make sure that this change completely gives you what you need? Does it result in installs to new locations we'll need to deal with? Should we expect that we'll have a growing number of alternate feeds as new LTSes get released?

My hunch is that we'll need a much more thorough set of changes than this to accommodate the new LTS feed, so we should probably sit down and figure out all of the ways it impacts things. What's the priority on this?

@shichen85

Copy link
Copy Markdown
Member Author

Indeed, the LTS 2026 version has its own installation path and appdata path, so we will have to factor those in for the other Stitch functions.

The priority is low on this one, as it only breaks the GitHub Action igor-setup if the user wants to infer the runtime from the yyp file. The workaround is to explicitly define the runtime version.

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