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

Add INNGEST_API_BASE_URL and INNGEST_EVENT_API_BASE_URL #378

Merged
merged 4 commits into from
Nov 6, 2023

Conversation

jpwilliams
Copy link
Member

@jpwilliams jpwilliams commented Nov 2, 2023

Summary

In addition to INNGEST_BASE_URL, adds INNGEST_API_BASE_URL and INNGEST_EVENT_API_BASE_URL.

No current users should have to use this, but this is useful for our own internal testing.

Checklist

  • Added a docs PR that references this PR N/A Internal
  • Added unit/integration tests N/A
  • Added changesets if applicable

@jpwilliams jpwilliams added prerelease/inngest Create snapshot releases for a PR for the "inngest" package. ⬆️ improvement Performance, reliability, or usability improvements labels Nov 2, 2023
@jpwilliams jpwilliams self-assigned this Nov 2, 2023
Copy link

changeset-bot bot commented Nov 2, 2023

🦋 Changeset detected

Latest commit: 02a1598

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
inngest Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@inngest-release-bot
Copy link
Collaborator

inngest-release-bot commented Nov 2, 2023

A user has added the prerelease/inngest label, so this PR will be published to npm with the tag pr-378. It will be updated with the latest changes as you push commits to this PR.

You can install this prerelease version with:

npm install inngest@pr-378

The last release was built and published from 02a1598.

@djfarrelly
Copy link
Member

My only thought and open question - should it be INNGEST_API_... and INNGEST_EVENT_API... or just INNGEST_EVENT...? 🤔

@jpwilliams jpwilliams changed the title Add INNGEST_API_BASE_URL and INNGEST_EVENT_BASE_URL Add INNGEST_API_BASE_URL and INNGEST_EVENT_API_BASE_URL Nov 3, 2023
@jpwilliams jpwilliams merged commit b83f925 into main Nov 6, 2023
22 checks passed
@jpwilliams jpwilliams deleted the split-env-vars branch November 6, 2023 11:48
jpwilliams pushed a commit that referenced this pull request Nov 6, 2023
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## inngest@3.4.2

### Patch Changes

- [#378](#378)
[`b83f925`](b83f925)
Thanks [@jpwilliams](https://github.com/jpwilliams)! - Add
`INNGEST_API_BASE_URL` and `INNGEST_EVENT_API_BASE_URL`, used for
internal testing

- [#382](#382)
[`0002afa`](0002afa)
Thanks [@tonyhb](https://github.com/tonyhb)! - Remove verbose event keys
warning

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
⬆️ improvement Performance, reliability, or usability improvements prerelease/inngest Create snapshot releases for a PR for the "inngest" package.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants