You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: RELEASE.md
+19Lines changed: 19 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,25 @@ Once the code has been merged into the `develop` branch on this repo, there are
5
5
- You should create a GitHub [tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging), with the appropriate version number. Typically, from `v21.06` onwards all tags are created following the Linux Ubuntu versioning convention which is the `YY.MM` format where `Y` is the year and `M` is the month of that year when that release was created.
6
6
- You should push the package to [PyPI](https://pypi.org/). Schematic is on PyPI as [schematicpy](https://pypi.org/project/schematicpy/). You can go through the following two sections for that.
7
7
8
+
## Steps
9
+
- Step 1: Open a pull request to merge the `main` branch to the `develop` branch:
10
+
- Click on the "Pull Request" tab on Github
11
+
- Click on the green button "New pull request"
12
+
- Select `main` as "base" and `develop` as "compare"
13
+
- Resolve conflicts
14
+
- Link all PRs and/or issues that are included in the release (example [here](https://github.com/Sage-Bionetworks/data_curator/pull/357))
15
+
16
+
- Step 2: Create a tag
17
+
`git tag <tag version> -m '<message>'`
18
+
19
+
- Step 3: Push the tag to main branch (this step assumes that you have checked out the main branch locally)
20
+
`git push origin <tag version>`
21
+
22
+
This should trigger the PYPI release workflow and release a new version of schematic to PYPI. You could check by cliking on the GitHub action log and login to your PYPI account (and select project `schematicpy`. Please note that you have to obtain access to `schematicpy` to be able to see it.)
23
+
24
+
>Note: if you make some mistakes and would like to delete a tag, try the following commands: `git push --delete origin <version number>` for deleting a tag remotely and `git tag -d <version number>` for deleting a tag locally.
25
+
26
+
8
27
## Release to Test PyPI _(optional)_
9
28
10
29
The purpose of this section is to verify that the package looks and works as intended, by viewing it on [Test PyPI](https://test.pypi.org/) and installing the test version in a separate virtual environment.
Copy file name to clipboardExpand all lines: api/openapi/api.yaml
+37Lines changed: 37 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -350,6 +350,43 @@ paths:
350
350
description: Check schematic log
351
351
tags:
352
352
- Manifest Operations
353
+
/get/datatype/manifest:
354
+
get:
355
+
summary: Retrieve asset view table as a dataframe.
356
+
description: Retrieve asset view table as a dataframe.
357
+
operationId: api.routes.get_manifest_datatype
358
+
parameters:
359
+
- in: query
360
+
name: input_token
361
+
schema:
362
+
type: string
363
+
nullable: false
364
+
description: Token
365
+
example: Token
366
+
required: true
367
+
- in: query
368
+
name: asset_view
369
+
schema:
370
+
type: string
371
+
nullable: false
372
+
description: ID of view listing all project data assets. For example, for Synapse this would be the Synapse ID of the fileview listing all data assets for a given project.(i.e. master_fileview in config.yml)
373
+
example: syn23643253
374
+
required: true
375
+
- in: query
376
+
name: manifest_id
377
+
schema:
378
+
type: string
379
+
nullable: false
380
+
description: Manifest ID
381
+
example: syn27600110
382
+
required: true
383
+
responses:
384
+
"200":
385
+
description: A list of json
386
+
"500":
387
+
description: Check schematic log.
388
+
tags:
389
+
- Manifest Operations
353
390
/storage/projects:
354
391
get:
355
392
summary: Get all storage projects the current user has access to
0 commit comments