Release 0.14.1 #145
Merged
Release 0.14.1 #145
Conversation
This file contains 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
References: Cyber-Domain-Ontology/CDO-Utility-Local-UUID#3 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
|
I'll need to restart this patch series to account for prerelease review. |
ajnelson-nist
force-pushed
the
release-0.14.1
branch
3 times, most recently
from
1990f70
to
2649290
Compare
ajnelson-nist
added a commit
that referenced
this pull request
Dec 19, 2023
This enables release review for releases that precede the current release. This was found necessary from efforts on PR 145. References: * #145 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
|
The PR has been updated to reduce its scope and update an element of the GitHub Actions programming. It seems these are necessary to do the initially-planned prior releases. |
This patch isolates a change needed to get patch-releases atop 0.5.0 to pass `make check`. This patch alone will not pass `make check`; see the following octopus merge for a commit that passes `make check`. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.5.0 to pass Continuous Integration. This patch alone will not pass CI; see the following octopus merge for a commit that passes CI. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.5.0 to pass `make check`. This patch alone will not pass `make check`; see the following octopus merge for a commit that passes `make check`. No effects were observed on Make-managed files. References: * ucoProject/UCO#373 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch backports PR 99. This patch isolates a change needed to get patch-releases atop 0.5.0 to pass Continuous Integration. This patch alone will not pass CI; see the following octopus merge for a commit that passes CI. References: * #99 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
…sh_pre_commit', 'HotFix-0.5.1-set_rdflib-ceiling' and 'HotFix-0.5.1-add_local_rdf_toolkit' into release-0.5.1 This octopus merge brings in four isolated changes that do not individually pass `make check` and the Continuous Integration process on GitHub, but taken together, they do pass the test processes. The patches were written individually for change-explainability, and for a planned reversion of one part as catch-up patch releases are made. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This enables release review for releases that precede the current release. This was found necessary from efforts on PR 145. Cherry pick extra effects: This patch also cleans up some dangling whitespace flagged by `git diff`. References: * #145 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov> (cherry picked from commit f560e2e)
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.6.0 to pass Continuous Integration. This patch alone will not pass CI; see the following octopus merge for a commit that passes CI. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.7.0 to pass `make check`. This patch alone will not pass `make check`; see the following octopus merge for a commit that passes `make check`. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
|
I was incorrect on the GitHub interface programming bit. To enable Actions for So, this PR is going to get another force-push from its current state after some other PRs are resolved. |
This is a squashed commit of the non-syntax changes from PR 59. References: * #59 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Merged
Release 0.5.1
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * https://packaging.python.org/en/latest/specifications/version-specifiers/#post-release-separators Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
…into release-0.6.1
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This reverts commit 63afdfc.
No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.6.0 to pass Continuous Integration. This patch alone will not pass CI; see the following octopus merge for a commit that passes CI. No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This patch isolates a change needed to get patch-releases atop 0.9.0 to pass `make check`. This patch alone will not pass `make check`; see the following octopus merge for a commit that passes `make check`. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
…andas_ceiling' and 'support-0.8.x' into release-0.9.1
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
ajnelson-nist
force-pushed
the
release-0.14.1
branch
from
f560e2e
to
156d81e
Compare
|
This PR is ready for review and merge once CI passes. The sibling PR into |
|
I'll handle stamping the 0.7.1 ... 0.14.1 releases after this is merged. |
kchason
approved these changes
Dec 22, 2023
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.
Review notes for this PR:
case-utils0.5.0, mostly following the Git-Flow practice for HotFix branches. The initial patch was made frommainat 0.5.0. However, the original 2010 documentation page does not include practices for HotFix patches on releases older than the current release. Other documentation, e.g. here1, demonstrates "Support" branches, but not a general practice on how to finally "Catch up" to the currentmain. (This is not intended as a criticism - it just seems there remains creative latitude in how to do so.)pre-commitpackages encountering a known issue around that time. So, as necessary scope creep, the backported fixes include runningpre-commit autoupdatefairly early on.mainfor a 0.14.1 release, and a sibling PR will targetdevelopto apply the HotFix todevelopand PR Additional parts for exportinglocal_uuid#144 .Footnotes
Participation by NIST in the creation of the documentation of mentioned software is not intended to imply a recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that any specific software is necessarily the best available for the purpose. ↩