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
https://github.com/ni/measurement-plugin-python/wiki/Release-Process has manual pre/post-release steps dealing with example versioning. I think we can simplify this by leaving the path = "../../..." dev-dependencies uncommented in the Git repo and updating the publish workflow to comment them out before building the examples .zip file. This is basically what we have been doing with packages/generator for the 2.1.0 release.
The current process was established before we started building a separate examples .zip file. At that time, users were expected to obtain the examples by cloning the Git repo or downloading the per-release .zip file containing the entire Git repo checked out at the release tag. Now that we are building a separate examples .zip file, we can modify the examples before zipping them up.
Note that you can use poetry install --only main to ignore dev-dependencies.
Tech Debt
https://github.com/ni/measurement-plugin-python/wiki/Release-Process has manual pre/post-release steps dealing with example versioning. I think we can simplify this by leaving the
path = "../../..."
dev-dependencies uncommented in the Git repo and updating the publish workflow to comment them out before building the examples .zip file. This is basically what we have been doing with packages/generator for the 2.1.0 release.The current process was established before we started building a separate examples .zip file. At that time, users were expected to obtain the examples by cloning the Git repo or downloading the per-release .zip file containing the entire Git repo checked out at the release tag. Now that we are building a separate examples .zip file, we can modify the examples before zipping them up.
Note that you can use
poetry install --only main
to ignore dev-dependencies.Cc: @dixonjoel @rajatkumar87
AB#2903024
The text was updated successfully, but these errors were encountered: