pepscript 0.1.0__tar.gz → 0.1.1__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: pepscript
3
- Version: 0.1.0
3
+ Version: 0.1.1
4
4
  Summary: Typed Python library for working with PEP 723 inline script metadata
5
5
  Keywords: pep723,metadata,inline-script,toml
6
6
  Author: maximiliancw
@@ -14,6 +14,8 @@ Classifier: Programming Language :: Python :: 3.13
14
14
  Classifier: Typing :: Typed
15
15
  Requires-Python: >=3.12
16
16
  Project-URL: Repository, https://github.com/botlot-project/PEPscript
17
+ Project-URL: Documentation, https://botlot-project.github.io/PEPscript/
18
+ Project-URL: Issues, https://github.com/botlot-project/PEPscript/issues
17
19
  Description-Content-Type: text/markdown
18
20
 
19
21
  # PEPScript
@@ -120,14 +122,15 @@ uv run ty check . # Type check
120
122
  ### Versioning and releases
121
123
 
122
124
  This project uses [Semantic Versioning](https://semver.org/). The version is set in `pyproject.toml`.
125
+ Release notes are generated automatically from [Conventional Commits](https://www.conventionalcommits.org/) when a version tag is pushed.
123
126
 
124
127
  To release:
125
128
 
126
129
  1. Update `version` in `pyproject.toml`
127
130
  2. Tag and push:
128
131
  ```bash
129
- git tag v0.2.0
130
- git push --tags
132
+ git tag v0.1.1
133
+ git push origin v0.1.1
131
134
  ```
132
135
 
133
136
  Commit messages should follow [Conventional Commits](https://www.conventionalcommits.org/) (`fix:`, `feat:`, `feat!:` for breaking changes).
@@ -102,14 +102,15 @@ uv run ty check . # Type check
102
102
  ### Versioning and releases
103
103
 
104
104
  This project uses [Semantic Versioning](https://semver.org/). The version is set in `pyproject.toml`.
105
+ Release notes are generated automatically from [Conventional Commits](https://www.conventionalcommits.org/) when a version tag is pushed.
105
106
 
106
107
  To release:
107
108
 
108
109
  1. Update `version` in `pyproject.toml`
109
110
  2. Tag and push:
110
111
  ```bash
111
- git tag v0.2.0
112
- git push --tags
112
+ git tag v0.1.1
113
+ git push origin v0.1.1
113
114
  ```
114
115
 
115
116
  Commit messages should follow [Conventional Commits](https://www.conventionalcommits.org/) (`fix:`, `feat:`, `feat!:` for breaking changes).
@@ -1,6 +1,6 @@
1
1
  [project]
2
2
  name = "pepscript"
3
- version = "0.1.0"
3
+ version = "0.1.1"
4
4
  description = "Typed Python library for working with PEP 723 inline script metadata"
5
5
  readme = "README.md"
6
6
  license = "MIT"
@@ -21,6 +21,8 @@ classifiers = [
21
21
 
22
22
  [project.urls]
23
23
  Repository = "https://github.com/botlot-project/PEPscript"
24
+ Documentation = "https://botlot-project.github.io/PEPscript/"
25
+ Issues = "https://github.com/botlot-project/PEPscript/issues"
24
26
 
25
27
  [dependency-groups]
26
28
  dev = [
File without changes