Repository navigation
Release: promote jvspatial 0.1.0 compatible jvagent RC - #250
Merged
Merged
Conversation
Adapt jvagent to secure jvspatial entity fields
# Conflicts: # .planning/reference/jvspatial-integration.md # jvagent/version.py # pyproject.toml # requirements-all.txt # requirements.txt
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
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.
Purpose
Promote merged jvagent #249 from
devintomainso0.1.8rc19can be tagged and published to TestPyPI. This is the compatible candidate for publishedjvspatial==0.1.0and unblocks Integral Core's clean artifact gate.Integration
devwith currentmain, retaining the0.1.8rc19andjvspatial==0.1.0pins across package metadata and both requirements files.0.0.22version statement.0.1.8rc18release history.Gates
jvagent==0.1.8rc19against the published jvspatial wheel.