Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Orchestrator package not showing up in package manager #7112

Closed
2 of 8 tasks
darrenj opened this issue Apr 19, 2021 · 2 comments · Fixed by #7243
Closed
2 of 8 tasks

Orchestrator package not showing up in package manager #7112

darrenj opened this issue Apr 19, 2021 · 2 comments · Fixed by #7243
Assignees
@taicchoumsft
Labels
Area: Orchestrator P1 Painful if we don't fix, won't block releasing Type: Bug Something isn't working

Comments

@darrenj
Copy link

darrenj commented Apr 19, 2021

Describe the bug

Orchestrator package doesn't show up in Package Manager - in the default npm feed. If you switch to community then it does show up but it's not a community package?

image

image

Version

1.4.0-nightly.236490

Browser

  • Electron distribution
  • Chrome
  • Safari
  • Firefox
  • Edge

OS

  • macOS
  • Windows
  • Ubuntu

To Reproduce

Steps to reproduce the behavior:

  1. Go to package manager
  2. Orchestrator not shown
  3. Switch to community feed

Expected behavior

  • Shows up in main feed
@darrenj darrenj added Type: Bug Something isn't working Needs-triage A new issue that require triage labels Apr 19, 2021
@taicchoumsft taicchoumsft self-assigned this Apr 20, 2021
@taicchoumsft taicchoumsft added Area: Orchestrator P1 Painful if we don't fix, won't block releasing and removed Needs-triage A new issue that require triage labels Apr 20, 2021
@taicchoumsft
Copy link
Contributor

taicchoumsft commented Apr 20, 2021 •
edited
Loading

Current nuget query is microsoft.bot.components+tags:msbot-component.

Suggest changing to microsoft.bot+tags:msbot-content,msbot-recognizer,msbot-action, these tags were added by @carlosscastro to SDK. Does this work @benbrown , @peterinnesmsft ?

image

We probably should then remove Microsoft packages from community, that's probably another work item I think.

@benbrown
Copy link
Contributor

I think all components, regardless of type, are supposed to have msbot-component.

@taicchoumsft taicchoumsft mentioned this issue Apr 22, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@taicchoumsft taicchoumsft

Labels
Area: Orchestrator P1 Painful if we don't fix, won't block releasing Type: Bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: adjust package manager feeds microsoft/BotFramework-Composer
3 participants
@benbrown @darrenj @taicchoumsft