-
Notifications
You must be signed in to change notification settings - Fork 56
Closed
Labels
Description
Checklist
1. Version bump
- Create a release branch from main branch. Name it "Rel#.#.#".
- Update version in package.json in release branch
- Update CHANGELOG.md with changes made in release branch.
- Create a release with tag from release branch. Name it "vscode-ai-foundry@#.#.#", e : vscode-ai-foundry@1.0.0. It will trigger CI/CD GitHub action to build a vsix file.
- Run through the Testing Checklist below using the vsix file.
2. Testing Checklist
Make sure that you have login with an Azure account in VS Code and have a project in Azure AI Foundry.
Tree view
- View Agents and Models in Azure Resources under Azure AI Foundry.
- The models and agent can be listed in tree view.
Agents
- Create a new agent file from tree view. 'Open Agent Designer' with agent file.
- Make changes in designer and save to local. Such as add/delete tools(bing/code interpreter/file search/openapi) to the agent.
- Deploy to Azure AI Foundry.
- Open agent playground. Try agent with bing/code interpreter/file search tool type.
Model Catalog
- Open Model Catalog
- Search for a model, deploy in Azure
Models
Besides the 'open in playground' item, which is exclusive to the Tree view, other items can be accessed not only from the Tree view but also through command Azure AI Foundry: XXX triggers.
- Deploy new AI model
- Open Code file
- Open in Playground
- Copy API Key
- Copy Endpoint
- Delete Model
If hotfixes are required before release
- Make the hotfix change in main branch, then create a new release with minor version number changed.
- Test any affected areas from the Testing Checklist
3. Release to marketplace
- Copy release pipeline's run id in GitHub action.
- Trigger the code sign pipeline in the Azure DevOps.
- Trigger the publish pipeline in the Azure DevOps. This pipeline won't release until manager approve.
- Approve the
Publishstep in pipeline to allow the pipeline to upload/publish the vsix to the marketplace. - Download the latest version from the marketplace (note, it may take up to 30 minutes and restarting vscode multiple times to force it to refresh the marketplace). Do a quick test to ensure the extension works as expected.
Reactions are currently unavailable