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

[Snyk] Upgrade @leanix/reporting from 0.3.7 to 0.4.2 #37

Closed

Conversation

snyk-bot
Copy link

Snyk has created this PR to upgrade @leanix/reporting from 0.3.7 to 0.4.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 3 versions ahead of your current version.
  • The recommended version was released 2 months ago, on 2020-02-25.
Release notes
Package name: @leanix/reporting
  • 0.4.2 - 2020-02-25
    • Added details of the current user viewing the report to the settings sent to the report on init.
  • 0.4.1 - 2020-02-19
  • 0.4.0 - 2020-02-18
    • Added lx.showLegend() to allow reports to show a custom legend above the report.
    • Clarified that lx.executeParentOriginXHR only supports GET requests.
    • Removed an unused argument from lx.showSpinner().
    • Improved the documentation by limiting it to public methods and properties and by providing better function signatures and syntax highlighting.
  • 0.3.7 - 2020-02-17

    The single select Form field used when calling openFormModal receives options with a value and label object, instead of a string. Thus, each option can be identified easily.

from @leanix/reporting GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants