chore(shared-data): command schema bump version to 13#17889
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## edge #17889 +/- ##
=======================================
Coverage 24.57% 24.57%
=======================================
Files 2936 2936
Lines 225163 225163
Branches 18920 18920
=======================================
Hits 55345 55345
Misses 169806 169806
Partials 12 12
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
emilyburghardt
pushed a commit
that referenced
this pull request
Mar 31, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
smb2268
pushed a commit
that referenced
this pull request
Mar 31, 2025
This change that was made to command schema 12 - the command schema releasing with Robot Stack v8.4.0 - needs to be added to the edge current version schema of 13. ```shell cd api make command-schema ``` see #17889
emilyburghardt
pushed a commit
that referenced
this pull request
Apr 1, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
andySigler
pushed a commit
that referenced
this pull request
Apr 1, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
emilyburghardt
pushed a commit
that referenced
this pull request
Apr 2, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
caila-marashaj
pushed a commit
that referenced
this pull request
Apr 8, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
caila-marashaj
pushed a commit
that referenced
this pull request
Apr 11, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
caila-marashaj
pushed a commit
that referenced
this pull request
Apr 11, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
caila-marashaj
pushed a commit
that referenced
this pull request
Apr 11, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 16, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back.
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 17, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 19, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 19, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 19, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 20, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 20, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 22, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 23, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 24, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 24, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 29, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 29, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
ddcc4
pushed a commit
that referenced
this pull request
May 29, 2025
Since we have isolated Robot Stack release 8.4 into `chore_release-8.4.0` we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done in `chore_release-8.4.0` then incorporated in `edge` via a merge back. (cherry picked from commit 1e70394)
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
2 participants
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.
Overview
Since we have isolated Robot Stack release 8.4 into
chore_release-8.4.0we must lock down command schema 12 for that Robot Stack Release. If changes are needed to command schema 12 they must first be done inchore_release-8.4.0then incorporated inedgevia a merge back.I produced the new schema version by running
cd api python -m pipenv run python src/opentrons/protocol_engine/commands/generate_command_schema.py 13 --overwrite-shared-dataReview requests
Risk assessment
Medium rare 🍖 - need validation this is all the steps and that all tests pass.