-
Notifications
You must be signed in to change notification settings - Fork 29
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
bump to v31.1.0 #287
bump to v31.1.0 #287
Changes from all commits
4325cab
eace7ca
722ecf8
437ddcc
b2348c7
59484e4
514c026
51242e8
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,6 @@ | ||
{ | ||
"name": "dash-ag-grid", | ||
"version": "31.0.1", | ||
"version": "31.2.0", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Chatted with @alexcjohnson -- I was wrong with the version bump; we follow the major version of Ag Grid only, so this would be a minor bump to There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @ndrezn and @alexcjohnson The main purpose of matching the the AG Grid versions is to give people an easy way to know the underlying AG Grid version. This makes it easier to know what version of their docs to use. This is important especially for Enterprise users because we have so few AG Grid Enterprise features documented. Even in minor releases AG Grid adds a lot of features (especially Enterprise features) and deprecates props. I think it's helpful to match their release numbers as closely as possible. Given their rapid release schedule, I doubt we would ever need to release our own minor version before they would have another one out anyway. Would you reconsider and make this release 31.2.0? |
||
"description": "Dash wrapper around AG Grid, the best interactive data grid for the web.", | ||
"repository": { | ||
"type": "git", | ||
|
@@ -31,9 +31,9 @@ | |
"dependencies": { | ||
"@emotion/react": "^11.11.3", | ||
"@emotion/styled": "^11.11.0", | ||
"ag-grid-community": "31.1.1", | ||
"ag-grid-enterprise": "31.1.1", | ||
"ag-grid-react": "31.1.1", | ||
"ag-grid-community": "31.2.1", | ||
"ag-grid-enterprise": "31.2.1", | ||
"ag-grid-react": "31.2.1", | ||
ndrezn marked this conversation as resolved.
Show resolved
Hide resolved
|
||
"@mui/icons-material": "^5.15.7", | ||
"@mui/material": "^5.15.7", | ||
"d3-format": "^3.1.0", | ||
|
@@ -85,4 +85,4 @@ | |
"browserslist": [ | ||
"last 7 years and not dead" | ||
] | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There should be a new version number added rather than
unreleased
similar to othersThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unreleased swaps to version number with the release of the new package, as we dont know what version these changes will be included in when adding. 😏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the release PR though?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, you make the release in a separate PR. Along with npm updates.