Skip to content

Fix Docker file release #2751

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

Merged
merged 2 commits into from
May 26, 2024
Merged

Fix Docker file release #2751

merged 2 commits into from
May 26, 2024

Conversation

TuvalSimha
Copy link
Collaborator

🚨 IMPORTANT: Please do not create a Pull Request without creating an issue first.

Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of
the pull request.

Description

Please include a summary of the change and which issue is fixed. Please also include relevant
motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as
    expected)
  • This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):

Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Test Environment:

  • OS:
  • @graphql-inspector/...:
  • NodeJS:

Checklist:

  • I have followed the
    CONTRIBUTING doc and the
    style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose
the solution you did and what alternatives you considered, etc...

Copy link

changeset-bot bot commented May 26, 2024

⚠️ No Changeset found

Latest commit: 072c792

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

Copy link
Contributor

github-actions bot commented May 26, 2024

🚀 Snapshot Release (alpha)

The latest changes of this PR are available as alpha on npm (based on the declared changesets):

Package Version Info
@graphql-inspector/action 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/ci 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/cli 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/audit-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/coverage-command 6.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/diff-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/introspect-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/serve-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/similar-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/validate-command 5.0.5-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/core 6.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/code-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/git-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/github-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/graphql-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/json-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/loaders 4.0.4-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/url-loader 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎
@graphql-inspector/logger 5.0.1-alpha-20240526145450-072c7921fb7e2d4e13f34e4d489ce5adb6c50fd5 npm ↗︎ unpkg ↗︎

Copy link
Contributor

github-actions bot commented May 26, 2024

💻 Website Preview

The latest changes are available as preview in: https://16b8d79b.graphql-inspector.pages.dev

@TuvalSimha TuvalSimha merged commit 1b25cc6 into master May 26, 2024
7 checks passed
@TuvalSimha TuvalSimha deleted the docker-and-tuval branch May 26, 2024 14:57
DanteUkraine pushed a commit to DanteUkraine/graphql-inspector that referenced this pull request May 27, 2024
* Fix Docker file release

* prettier
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.

1 participant