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

oidc-signin-tool: log signin retries #256

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

paulius-valiunas
Copy link
Collaborator

No description provided.

@@ -31,28 +31,28 @@
"directory": "packages/browser"
},
"dependencies": {
"@itwin/core-common": "^3.7.0 || ^4.0.0",
"@itwin/core-common": "^4.9.1",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This intended?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar changes exist in other packages.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just ran pnpm update and this happened... this should probably be a peerDependency. Having a wide range in dependencies doesn't guarantee it will be shared with the parent package, most likely pnpm would just install 4.9.1 even with the current version range.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I just looked through the source and found that only a type is imported from this package, so it should definitely be a devDependency, or a peerDependency... but definitely not a direct dependency. Either way, this change does not affect consumers in any way, because as I said, pnpm would pick the latest version in that range anyway.

@ben-polinsky
Copy link
Collaborator

@paulius-valiunas my attempts to fix the integration tests in #257 have not gone as planned. I'll keep at it tomorrow

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.

4 participants