Prepare 1.0.0 release
Open
- Dominant language
- Python
- Stars
- 23
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
We should make a 1.0.0 release.
There may need to be breaking code changes, so now is the time to pin <1.0.0 in downstream libraries
Contributor guide
Research direction
The issue names no files, tests, or release entry points. Start by reviewing the repository's release process and downstream libraries that depend on KGCL, then determine the required breaking changes and version constraints. Done means a coordinated 1.0.0 release with downstream libraries pinned below 1.0.0 where needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100