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

Remove 'pluginVersion' and 'pluginName' from nodejs schema options. #13646

Merged
merged 1 commit into from Aug 8, 2023

Conversation

Frassle
Copy link
Member

@Frassle Frassle commented Aug 3, 2023

Description

These options should be unused, and it appears the only use case we have of them is a couple of tests.
Given that these options were only exposed to NodeJS there was no sensible way for users to make use of them, as all the other SDKs would still have used the top level plugin name and version declared by the schema.

Checklist

  • I have run make tidy to update any new dependencies
  • I have run make lint to verify my code passes the lint check
    • I have formatted my code using gofumpt
  • I have added tests that prove my fix is effective or that my feature works
  • I have run make changelog and committed the changelog/pending/<file> documenting my change
  • Yes, there are changes in this PR that warrants bumping the Pulumi Cloud API version

@Frassle Frassle requested a review from a team August 3, 2023 22:17
@pulumi-bot
Copy link
Contributor

pulumi-bot commented Aug 3, 2023

Changelog

[uncommitted] (2023-08-08)

Miscellaneous

  • [sdkgen/nodejs] Remove the pluginVersion and pluginName options from nodejs schema options.
    #13646

@abhinav
Copy link
Contributor

abhinav commented Aug 7, 2023

build failure should be fixed now. rebase on master, please.

@Frassle Frassle force-pushed the fraser/rmPluginVersionNameNodeJS branch from f00b5f8 to 9049610 Compare August 8, 2023 11:19
@Frassle
Copy link
Member Author

Frassle commented Aug 8, 2023

bors merge

@bors
Copy link
Contributor

bors bot commented Aug 8, 2023

🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set.

@bors
Copy link
Contributor

bors bot commented Aug 8, 2023

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

@bors bors bot merged commit 9ef3b11 into master Aug 8, 2023
56 checks passed
@bors bors bot deleted the fraser/rmPluginVersionNameNodeJS branch August 8, 2023 12:20
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.

None yet

3 participants