Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Prepare release v0.0.10#127

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
vinikatyal wants to merge1 commit intomain
base:main
Choose a base branch
Loading
fromvk/release0.0.10
Open

Prepare release v0.0.10#127

vinikatyal wants to merge1 commit intomainfromvk/release0.0.10

Conversation

@vinikatyal
Copy link
Contributor

Description

  • What is this PR about?

Screenshots/Results

  • Add a screenshot of the changes or code responses

Reference Links

  • Links to JIRA issue, links, Slack discussions, etc.

Checklist

This PR includes the following (tick all that apply):

  • Tests added/updated for new/changed functionality
  • Bug Fix (explain the bug in the description)
  • Refactoring or optimizations (no functional changes)
  • Documentation updated (README, docstrings, etc.)
  • Build or deployment related changes
  • Dependency updates (requirements.txt/pyproject.toml)
  • Setup change (update README/setup instructions if required)
  • Code style checks passed (PEP8, flake8, black, etc.)
  • Type hints added/updated (if applicable)
  • Pre-commit hooks run (if configured)

@vinikatyal
Copy link
ContributorAuthor

Hi@kaushik-himself is this release number fine?

@kaushik-himself
Copy link
Contributor

@vinikatyal you need to follow the release process defined in our docs:https://github.com/fiddlecube/compliant-llm/blob/main/docs/releaseguide.md#release-process

  • first, create a pre-release and test it
  • patch version needs to be updated: first 0.0.10-alpha1
  • this will release an alpha version to test pypi:
  • follow the steps to push the commit and also the tag to origin to release the alpha version to test pypi
  • if the tests succeed, move ahead with the release
  • else, fix the issues and create a new alpha version, say 0.0.10-alpha2

Release:

  • Same steps as pre-release. but version doesn't have the-alphaN at the end.
  • this will push a new version to pypi
  • install and test the new version by runningpip install compliant-llm==0.0.10.

Note: as soon as you push the git tag to origin, the version is released.

We can block time on the calendar to do this over a meeting, if that will make it easier.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@kaushik-himselfkaushik-himselfAwaiting requested review from kaushik-himself

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@vinikatyal@kaushik-himself

[8]ページ先頭

©2009-2025 Movatter.jp