| Name | releaseherald JSON |
| Version |
0.1.0
JSON |
| download |
| home_page | |
| Summary | Git tag based release note generator |
| upload_time | 2023-08-03 13:01:36 |
| maintainer | |
| docs_url | None |
| author | |
| requires_python | >=3.7 |
| license | Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. |
| keywords |
releasenotes
release
whatsnew
git
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# Introduction
`releaseherald` is a utility that can generate release notes. The only help it needs from
developers is to collect meaningful news fragments in a directory, and apply consistent tags.
We believe releasenotes are an important aspect of a project, they should be convenient to read and easy to work with.
Ideally every pull request should come with an update of the releasenotes, if this
is a single file then one always run into merge conflicts, but if each PR has its own news fragment then this is easily
avoidable. `releaseherald` is designed to be easy to extend, and there are just three guiding principals:
- version control in git
- the release notes for a version is fabricated from the news fragments created/modified between the two release
- the release number can be worked out from git tags
Releaseherald was inspired by [towncrier's philosophy](https://github.com/twisted/towncrier#Philosophy).
## Concept
The below diagram explains the concept and shows off the various data that flows into `releaseherald`.
```mermaid
%% Unfortunately PyPi does not render this diagram so just please scroll it through
flowchart LR
subgraph G[Git Repo]
subgraph L1[Change since TAG 0.9.1]
direction LR
L1C3[Commit 3 TAG: 1.0.0]
L1C2[Commit 2]
L1C1[Commit 1]
C3N2[news4.srt]
C3N1[news3.srt]
C2N1[news2.srt]
C1N1[news1.srt]
L1C3 --- C3N2
L1C3 --- C3N1
L1C2 --- C2N1
L1C1 --- C1N1
end
subgraph L2 [Change since TAG 0.7.0]
direction LR
L2C3[Commit 3 TAG: 0.9.1]
L2C2[Commit 2]
L2C1[Commit 1]
L2C3N1[news3.srt]
L2C2N1[news2.srt]
L2C1N1[news1.srt]
L2C3 --- L2C3N1
L2C2 --- L2C2N1
L2C1 --- L2C1N1
end
subgraph L3 [Earlier changes]
direction LR
L3C2[Commit N TAG: 0.7.0 ...]
end
end
subgraph S[Sourcetree]
RC[releaseherald.toml\nconfiguration]
RT["releasenote_template\n\nVersion {version_num}\n{list_of_news ...}"]
subgraph PRN[Previous releasenotes]
direction LR
PRNP[#Placeholder#]
PRN1[Version 0.7.0 ...]
PRN2[Version 0.6.3 ...]
PRN2[Version 0.6.0 ...]
end
end
RH[Releaseherald]
L1 --> RH
L2 --> RH
RC --> RH
RT ---> RH
PRN ---> RH
subgraph N[New releasenotes]
direction LR
NRNP[#Placeholder#]
NRN1[Version 1.0.0\nnews1\nnews2\nnews3\nnews4]
NRN2[Version 0.9.1\nnews1\nnews2\nnews3]
NRN3[Version 0.7.0 ...]
NRN4[Version 0.6.3 ...]
NRN5[Version 0.6.0 ...]
end
RH --> N
N --> RE[Send in email]
N --> RU[Add to GitHub release]
N --> RS[Update in source and commit to git]
style L1 fill:#f003
style NRN1 fill:#f003
style L2 fill:#0f03
style NRN2 fill:#0f03
```
## Install
it can be installed into the python venv
```sh
pip install releaseherald
```
or if you like it better globally, use pipx
```sh
pipx install releaseherald
```
## Basics
`releaseherald` is a command line tool it needs python 3.7+ to run. It needs a config file in the root of the git repo
it should be called `releaseherald.toml`. If it is used in a python project it can read it's configuration
from `pyproject.toml` from `[tool.releaseherald]`. It is possible to start without any configuration, then one needs to
create a `news_fragment` directory in the root of the git repo and a `news.rst` file which should contain a news file
something like this:
```rst
Release Notes
=============
.. releaseherald_insert
```
As `releaseherald` working with diffs between tags so if no tags yet in the repo just create one
named `RELEASEHERALD_ROOT`. News fragments should be added to the `nesw_fragment` directory, committing them, and
merged (preferably with a pull request). When releasing, a tag need to be created with
following [semantic versioning](https://semver.org/) principles. Once there are some commits and news fragments release
notes can be generated as `releaseherald generate`. This will result something like this:
```rst
Release Notes
=============
.. releaseherald_insert
1.0.0 (2021-10-15)
------------------
* 1, before first release
* 2, before first release
```
This tool try not to have many opinions, so all the above defaults can be tweaked through configuration or command line.
New fragments do not need to be removed between releases, no need to commit the generated release notes either,
as `releaseherald`
works that out from git history, though if that fits better to the workflow it can be done.
Raw data
{
"_id": null,
"home_page": "",
"name": "releaseherald",
"maintainer": "",
"docs_url": null,
"requires_python": ">=3.7",
"maintainer_email": "",
"keywords": "releasenotes,release,whatsnew,git",
"author": "",
"author_email": "Morgan Stanley <eti-testplan@morganstanley.com>",
"download_url": "https://files.pythonhosted.org/packages/aa/0b/dab36edd4da4d3724afe82ed932f43873c9c7910dccf164dd1b638bd8c3a/releaseherald-0.1.0.tar.gz",
"platform": null,
"description": "# Introduction\n\n`releaseherald` is a utility that can generate release notes. The only help it needs from\ndevelopers is to collect meaningful news fragments in a directory, and apply consistent tags.\n\nWe believe releasenotes are an important aspect of a project, they should be convenient to read and easy to work with.\nIdeally every pull request should come with an update of the releasenotes, if this\nis a single file then one always run into merge conflicts, but if each PR has its own news fragment then this is easily\navoidable. `releaseherald` is designed to be easy to extend, and there are just three guiding principals:\n\n- version control in git\n- the release notes for a version is fabricated from the news fragments created/modified between the two release\n- the release number can be worked out from git tags\n\nReleaseherald was inspired by [towncrier's philosophy](https://github.com/twisted/towncrier#Philosophy).\n \n\n## Concept\n\nThe below diagram explains the concept and shows off the various data that flows into `releaseherald`.\n\n```mermaid\n%% Unfortunately PyPi does not render this diagram so just please scroll it through\n\nflowchart LR\n subgraph G[Git Repo]\n subgraph L1[Change since TAG 0.9.1]\n direction LR\n\n L1C3[Commit 3 TAG: 1.0.0]\n L1C2[Commit 2]\n L1C1[Commit 1]\n\n C3N2[news4.srt]\n C3N1[news3.srt]\n C2N1[news2.srt]\n C1N1[news1.srt]\n\n L1C3 --- C3N2\n L1C3 --- C3N1\n L1C2 --- C2N1\n L1C1 --- C1N1\n\n\n end\n\n subgraph L2 [Change since TAG 0.7.0]\n direction LR\n L2C3[Commit 3 TAG: 0.9.1]\n L2C2[Commit 2]\n L2C1[Commit 1]\n\n L2C3N1[news3.srt]\n L2C2N1[news2.srt]\n L2C1N1[news1.srt]\n\n L2C3 --- L2C3N1\n L2C2 --- L2C2N1\n L2C1 --- L2C1N1\n end\n subgraph L3 [Earlier changes]\n direction LR\n L3C2[Commit N TAG: 0.7.0 ...]\n end\n\n end\n\n subgraph S[Sourcetree]\n RC[releaseherald.toml\\nconfiguration]\n RT[\"releasenote_template\\n\\nVersion {version_num}\\n{list_of_news ...}\"]\n subgraph PRN[Previous releasenotes]\n direction LR\n PRNP[#Placeholder#]\n PRN1[Version 0.7.0 ...]\n PRN2[Version 0.6.3 ...]\n PRN2[Version 0.6.0 ...]\n end\n end\n\n\n RH[Releaseherald]\n\n L1 --> RH\n L2 --> RH\n\n RC --> RH\n RT ---> RH\n PRN ---> RH\n\n subgraph N[New releasenotes]\n direction LR\n NRNP[#Placeholder#]\n NRN1[Version 1.0.0\\nnews1\\nnews2\\nnews3\\nnews4]\n NRN2[Version 0.9.1\\nnews1\\nnews2\\nnews3]\n NRN3[Version 0.7.0 ...]\n NRN4[Version 0.6.3 ...]\n NRN5[Version 0.6.0 ...]\n end\n\n RH --> N\n\n N --> RE[Send in email]\n N --> RU[Add to GitHub release]\n N --> RS[Update in source and commit to git]\n\n style L1 fill:#f003\n style NRN1 fill:#f003\n style L2 fill:#0f03\n style NRN2 fill:#0f03\n\n```\n\n## Install\n\nit can be installed into the python venv\n\n```sh\npip install releaseherald\n```\n\nor if you like it better globally, use pipx\n\n```sh\npipx install releaseherald\n```\n\n## Basics\n\n`releaseherald` is a command line tool it needs python 3.7+ to run. It needs a config file in the root of the git repo\nit should be called `releaseherald.toml`. If it is used in a python project it can read it's configuration\nfrom `pyproject.toml` from `[tool.releaseherald]`. It is possible to start without any configuration, then one needs to\ncreate a `news_fragment` directory in the root of the git repo and a `news.rst` file which should contain a news file\nsomething like this:\n\n```rst\nRelease Notes\n=============\n\n .. releaseherald_insert\n```\n\nAs `releaseherald` working with diffs between tags so if no tags yet in the repo just create one\nnamed `RELEASEHERALD_ROOT`. News fragments should be added to the `nesw_fragment` directory, committing them, and\nmerged (preferably with a pull request). When releasing, a tag need to be created with\nfollowing [semantic versioning](https://semver.org/) principles. Once there are some commits and news fragments release\nnotes can be generated as `releaseherald generate`. This will result something like this:\n\n```rst\nRelease Notes\n=============\n\n.. releaseherald_insert\n\n1.0.0 (2021-10-15)\n------------------\n\n* 1, before first release\n* 2, before first release\n```\n\nThis tool try not to have many opinions, so all the above defaults can be tweaked through configuration or command line.\nNew fragments do not need to be removed between releases, no need to commit the generated release notes either,\nas `releaseherald`\nworks that out from git history, though if that fits better to the workflow it can be done.\n",
"bugtrack_url": null,
"license": "Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. \"License\" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. \"Licensor\" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. \"Legal Entity\" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, \"control\" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. \"You\" (or \"Your\") shall mean an individual or Legal Entity exercising permissions granted by this License. \"Source\" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. \"Object\" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. \"Work\" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). \"Derivative Works\" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. \"Contribution\" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, \"submitted\" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as \"Not a Contribution.\" \"Contributor\" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a \"NOTICE\" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets \"[]\" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same \"printed page\" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the \"License\"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ",
"summary": "Git tag based release note generator",
"version": "0.1.0",
"project_urls": {
"Homepage": "https://github.com/morganstanley/releaseherald",
"Repository": "https://github.com/morganstanley/releaseherald.git"
},
"split_keywords": [
"releasenotes",
"release",
"whatsnew",
"git"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "8afe7e6bc0f3cc8739efa1ca314f253f92511543035b91e7b469dbc455a84627",
"md5": "9933231cb07f9569fb728d6361a8c8ad",
"sha256": "fcec58646ac4b9b320a97e2b9a7884eb361c2cdfbafe32a9739743aa1293c9df"
},
"downloads": -1,
"filename": "releaseherald-0.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "9933231cb07f9569fb728d6361a8c8ad",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.7",
"size": 27649,
"upload_time": "2023-08-03T13:01:34",
"upload_time_iso_8601": "2023-08-03T13:01:34.649660Z",
"url": "https://files.pythonhosted.org/packages/8a/fe/7e6bc0f3cc8739efa1ca314f253f92511543035b91e7b469dbc455a84627/releaseherald-0.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": "",
"digests": {
"blake2b_256": "aa0bdab36edd4da4d3724afe82ed932f43873c9c7910dccf164dd1b638bd8c3a",
"md5": "7facbfcd961cc55abdc27acfbc310f13",
"sha256": "ffc125145ca1a1379723d419760af4cc66baff428762d748106847b990aecf89"
},
"downloads": -1,
"filename": "releaseherald-0.1.0.tar.gz",
"has_sig": false,
"md5_digest": "7facbfcd961cc55abdc27acfbc310f13",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.7",
"size": 25185,
"upload_time": "2023-08-03T13:01:36",
"upload_time_iso_8601": "2023-08-03T13:01:36.652068Z",
"url": "https://files.pythonhosted.org/packages/aa/0b/dab36edd4da4d3724afe82ed932f43873c9c7910dccf164dd1b638bd8c3a/releaseherald-0.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-08-03 13:01:36",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "morganstanley",
"github_project": "releaseherald",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "releaseherald"
}
