Skip to content

fix: add type#38

Merged
rodorgas merged 1 commit into
mainfrom
fix/context-type
Aug 15, 2025
Merged

fix: add type#38
rodorgas merged 1 commit into
mainfrom
fix/context-type

Conversation

@rodorgas
Copy link
Copy Markdown
Contributor

What is the purpose of this pull request?

Types of changes

  • New feature (non-breaking change which adds functionality)
  • Refactor (non-breaking change which doesn't change any functionalities)
  • Bug fix (non-breaking change which fixes an issue)
  • Chore (changes configuration files, GitHub workflows, etc.)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Requires change to documentation, which has been updated accordingly.

@rodorgas rodorgas requested a review from allanbatista August 15, 2025 21:37
@vtex-io-ci-cd
Copy link
Copy Markdown

vtex-io-ci-cd Bot commented Aug 15, 2025

Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖

Please select which version do you want to release:

  • Patch (backwards-compatible bug fixes)

  • Minor (backwards-compatible functionality)

  • Major (incompatible API changes)

And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.

  • No thanks, I would rather do it manually 😞

@vtex-io-docs-bot
Copy link
Copy Markdown

Beep boop 🤖

I noticed you're not using the Docs Builder properly yet, if you need help to set that up please go to IO Documentation

@rodorgas rodorgas merged commit b902264 into main Aug 15, 2025
6 checks passed
@vtex-io-ci-cd
Copy link
Copy Markdown

vtex-io-ci-cd Bot commented Aug 15, 2025

Your PR has been merged! App is being published. 🚀
Version 2.10.3 → 2.10.4

After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:

vtex deploy vtex.adserver-resolver@2.10.4

After that your app will be updated on all accounts.

For more information on the deployment process check the docs. 📖

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