Skip to content

release: 0.0.1-alpha.1 #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

stainless-app[bot]
Copy link
Contributor

@stainless-app stainless-app bot commented Jan 9, 2025

Automated Release PR

0.0.1-alpha.1 (2025-01-09)

Full Changelog: v0.0.1-alpha.0...v0.0.1-alpha.1

Chores


This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

Summary by Sourcery

Prepare for initial release by updating installation instructions and version.

Enhancements:

  • Bump version to 0.0.1-alpha.1.

Chores:

  • Update repository URLs and references.

Copy link

sourcery-ai bot commented Jan 9, 2025

Reviewer's Guide by Sourcery

This PR prepares the project for its first alpha release by updating the installation instructions, version number, and repository URLs.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated installation instructions to point to the production repository.
  • Changed the installation command in the README and CONTRIBUTING files to use the production repository URL.
  • Updated the repository URL in the installation section of the README and CONTRIBUTING files from stainless-sdks/fireapi-v2-python to EvickaStudio/fireapi-v2.
README.md
CONTRIBUTING.md
Updated version number to 0.0.1-alpha.1.
  • Incremented version number in pyproject.toml.
  • Updated version string in src/fireapi_v2/_version.py.
pyproject.toml
src/fireapi_v2/_version.py
Updated repository URLs throughout the project.
  • Changed all instances of the staging repository URL to the production URL.
  • Updated links to the documentation, issue tracker, and repository in various files.
README.md
pyproject.toml
src/fireapi_v2/resources/accounts/accounts.py
src/fireapi_v2/resources/accounts/affiliate.py
src/fireapi_v2/resources/accounts/donations.py
src/fireapi_v2/resources/accounts/services.py
src/fireapi_v2/resources/domains/dns.py
src/fireapi_v2/resources/domains/domains.py
src/fireapi_v2/resources/kvm/backup.py
src/fireapi_v2/resources/kvm/config.py
src/fireapi_v2/resources/kvm/ddos.py
src/fireapi_v2/resources/kvm/kvm.py
src/fireapi_v2/resources/kvm/monitoring.py
src/fireapi_v2/resources/kvm/status.py
src/fireapi_v2/resources/kvm/traffic.py
src/fireapi_v2/resources/kvms/backup.py
src/fireapi_v2/resources/kvms/kvms.py
src/fireapi_v2/resources/webspaces.py
Added GitHub workflows for publishing to PyPI and checking the release environment.
  • Created a workflow to automate publishing to PyPI.
  • Added a workflow to check the release environment before publishing.
.github/workflows/publish-pypi.yml
.github/workflows/release-doctor.yml
Added and updated release-related files.
  • Created a changelog file to track changes between releases.
  • Added a release manifest file to track release progress.
  • Added a script to check the release environment.
  • Added a configuration file for release-please.
CHANGELOG.md
.release-please-manifest.json
bin/check-release-environment
release-please-config.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, stainless-app[bot]!). We assume it knows what it's doing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant