Skip to content
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

feat!: public release #41

Merged
merged 1 commit into from
Feb 13, 2024
Merged

feat!: public release #41

merged 1 commit into from
Feb 13, 2024

Conversation

ddneilson
Copy link
Contributor

@ddneilson ddneilson commented Feb 11, 2024

What was the problem/requirement? (What/Why)

We're about to publicly release this library. We need to prep the build process for that.

What was the solution? (How)

  • Update the build script to no longer define a PIP_INDEX_URL -- the environment variable
    that we used to interface with our internal repository during private development.
  • Update the code quality check to pull deps from the public PyPI, so
    that we're testing as customers would use it.
  • Use the public PyPI in the release flows since all deps are now
    available publicly. This ensures that the artifact we release can be
    built & used by anyone using PyPI.
  • Increment the openjd-model and openjd-sessions dependencies to the
    first publicly available versions.
  • Small additions to the README.

What is the impact of this change?

Release readiness

How was this change tested?

Just building the hatch environment.

Was this change documented?

Yes, it is documentation as well.

Is this a breaking change?

No, but it is being marked as one to force a minor version bump when we release.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@ddneilson ddneilson force-pushed the ddneilson/prep_release branch 9 times, most recently from d87b807 to 25cdd40 Compare February 13, 2024 15:24
@ddneilson ddneilson changed the title feat!: prepare for public release feat!: public release Feb 13, 2024
Preparing the repository for its public release:
- Update the build script to no longer define a PIP_INDEX_URL -- the environment variable
  that we used to interface with our internal repository during private development.
- Update the code quality check to pull deps from the public PyPI, so
  that we're testing as customers would use it.
- Use the public PyPI in the release flows since all deps are now
  available publicly. This ensures that the artifact we release can be
  built & used by anyone using PyPI.
- Increment the openjd-model and openjd-sessions dependencies to the
  first publicly available versions.
- Small additions to the README.

Signed-off-by: Daniel Neilson <53624638+ddneilson@users.noreply.github.com>
@ddneilson ddneilson force-pushed the ddneilson/prep_release branch from 25cdd40 to 5a6a956 Compare February 13, 2024 15:24
@ddneilson ddneilson marked this pull request as ready for review February 13, 2024 15:24
@ddneilson ddneilson requested a review from a team as a code owner February 13, 2024 15:24
@ddneilson ddneilson merged commit 88dd089 into mainline Feb 13, 2024
15 checks passed
@ddneilson ddneilson deleted the ddneilson/prep_release branch February 13, 2024 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants