microsoft / microsoft/Power-CAT-Copilot-Studio-Kit

Documentation: Upgrade instructions need to be updated to call out using the managed solution zip

Aperta
#653 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@psimolin ci sta già lavorando.

Dal 20/3/2026.

documentation
Lingua principale
TypeScript
Stelle
450
Fork
95
Merge medio
26m
PR unite (30g)
5

Descrizione

Description

Upgrade instructions - https://github.com/microsoft/Power-CAT-Copilot-Studio-Kit/blob/main/INSTALLATION_INSTRUCTIONS.md#upgrading-existing-solution

These state:
6. Select CopilotStudioKit.zip

However, on the releases page, you provide both the managed and unmanaged solution for download.

The instructions need to be updated to call out using the "CopilotStudioKit_XXXXXXX_managed.zip" file instead. Otherwise on import you get this warning:
"The solution is already installed on this system as a managed solution and the package supplied is attempting to install it in unmanaged mode. Import can only update solutions when the modes match. Uninstall the current solution and try again."

I understand that the section above upgrade/install for the download does call out to grab the managed version, but the instructions should be updated to match and be consistent. Especially since from the release page, if you click upgrade instructions, it jumps directly to that section, and users may not see the download note.

Optionally I would recommend move upgrading to its own .md file, then point back to install configurations steps if they are identical.

Steps to reproduce
  1. have managed solution installed
  2. try to update to unmanaged version
Expected behavior

Consistent messaging/wording through documentation.

Actual behavior

Instructions as written lead to an error.

Environment

No response

Additional context or logs

No response

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.