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

chore: bump functions esbuild config #58

Merged
merged 1 commit into from
Oct 29, 2024

Conversation

gabrielmpinto
Copy link
Contributor

Why?

Clear and short explanation here.

How?

  • Done A (replace with a breakdown of the steps)
  • Done B
  • Done C

Tickets?

Contribution checklist?

  • The commit messages are detailed
  • The build command runs locally
  • Assets or static content are linked and stored in the project
  • You have manually tested
  • You have provided tests

Security checklist?

  • Sensitive data has been identified and is being protected properly
  • Injection has been prevented (parameterized queries, no eval or system calls)

Preview?

Optionally, provide the preview url here

Copy link

changeset-bot bot commented Oct 29, 2024

⚠️ No Changeset found

Latest commit: 42798d8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@gabrielmpinto gabrielmpinto force-pushed the chore/bump-functions-esbuild-config branch from 42798d8 to 7c9a30e Compare October 29, 2024 23:16
@gabrielmpinto gabrielmpinto merged commit b889872 into develop Oct 29, 2024
3 checks passed
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.

2 participants