Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
Z
zlib_into
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
dataAnalysis
zlib_into
Graph
aa5488b1b54db5092c1ff5d363ec7acb857df1e4
Select Git revision
Branches
2
main
default
protected
unlimited-api-test-artifacts
Tags
2
0.2
protected
0.1
protected
4 results
You can move around the graph by using the arrow keys.
Begin with the selected commit
Created with Raphaël 2.2.0
12
Mar
10
Feb
7
24
Jan
23
10
9
Update URL in metadata
main
main
Version number -> 0.2.0
0.2
0.2
Merge branch 'unlimited-api' into 'main'
Switch back to PyMem_Raw functions for zlib to allocate & free memory
Skip abi3audit in CI
Build for each Python version rather than using limited API
Set PY_VERSION for publish job
unlimited-api-t…
unlimited-api-test-artifacts
How does Gitlab behave with conflicting artifacts?
Build for each Python version rather than using limited API
Install twine into venv to upload packages
0.1
0.1
Add CI job to publish to PyPI
Include tests in sdist
Add license text
More metadata
Autoformat test file
Use ValueError on insufficient space in output buffer
Add README
Try building in manylinux container to use auditwheel
Try with src/ layout
See if we can build packages on Gitlab CI
Add some tests
Add decompression
Support keyword & optional args
Better error messages
Initial commit
Loading