Release v0.4.1#310
Merged
Merged
Conversation
Updates the requirements on [azure-monitor-query](https://github.com/Azure/azure-sdk-for-python) to permit the latest version. - [Release notes](https://github.com/Azure/azure-sdk-for-python/releases) - [Commits](Azure/azure-sdk-for-python@azure-monitor-query_1.3.0...azure-monitor-query_2.0.0) --- updated-dependencies: - dependency-name: azure-monitor-query dependency-version: 2.0.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Updates the requirements on [azure-mgmt-cognitiveservices](https://github.com/Azure/azure-sdk-for-python) to permit the latest version. - [Release notes](https://github.com/Azure/azure-sdk-for-python/releases) - [Commits](Azure/azure-sdk-for-python@azure-mgmt-cognitiveservices_13.5.0...azure-mgmt-cognitiveservices_14.1.0) --- updated-dependencies: - dependency-name: azure-mgmt-cognitiveservices dependency-version: 14.1.0 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…4.0 (#246) Updates the requirements on [pandas](https://github.com/pandas-dev/pandas) to permit the latest version. - [Release notes](https://github.com/pandas-dev/pandas/releases) - [Commits](pandas-dev/pandas@v2.0.0...v3.0.3) --- updated-dependencies: - dependency-name: pandas dependency-version: 3.0.3 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
When `agentops.pipeline.prompt_deploy stage` runs in a PR-stage context (GitHub Actions `pull_request` event or Azure DevOps `BUILD_REASON=PullRequest`), the version it creates in the dev Foundry project now carries metadata `agentops:candidate=true`, `agentops:pr=<number>`, and `agentops:created_at=<ISO timestamp>`. This solves the auditability and naive-consumer concerns raised in issue #214 at the source: portal viewers can filter the Versions tab on `agentops:candidate` to separate abandoned PR candidates from deployed-of-record versions, and downstream consumers that resolve "latest" can refuse to pick up candidates. Deployed-of-record runs (push to main/develop/release/** or workflow_dispatch) are not tagged, so absence of `agentops:candidate` is the deployed-of-record signal. The PR/deploy workflow templates (GitHub Actions and Azure DevOps) and the prompt-agent quickstart tutorial are updated to describe the new contract. A scheduled cleanup workflow can land later as a follow-up filtering on the same tag if numeric accumulation in Foundry becomes painful. Closes #214 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
Release v0.4.1
Automated release branch created from
develop.What happened
release/v0.4.1created fromdevelopCHANGELOG.mdupdated: versioned section[0.4.1]added0.4.1(package.json, plugin.json, marketplace.json)Next steps
maingit tag v0.4.1 && git push origin v0.4.1git checkout develop && git merge main && git push origin developChecklist
v0.4.1pushed