-
Notifications
You must be signed in to change notification settings - Fork 2
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
Release 0.3.0 #168
Release 0.3.0 #168
Conversation
Signed-off-by: Jitendra Gundaniya <[email protected]>
Signed-off-by: Jitendra Gundaniya <[email protected]>
Signed-off-by: Nok <[email protected]>
Signed-off-by: Jitendra Gundaniya <[email protected]>
Signed-off-by: Sajid Alam <[email protected]>
…o 0.3.0 Signed-off-by: Sajid Alam <[email protected]>
4. Manually test if the artifact works (no automated tests yet) | ||
5. Manually upload to VSCode Marketplace and VSX Registry (Drag and Drop) | ||
|
||
To upload a release, you will need to be added as a contributor or owner for both VSCode Marketplace and VSX Registry. |
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.
Hope we can automate this soon #128
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.
#128 will only fix the problem partially. I have not explored if there is a way to release on VSX through a CLI / API yet.
The heavy work here is the manual testing part (i.e. trigger a click on flowchart etc), not so much on the Github Action.
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.
Let's go!!
Thanks @rashidakanchwala , let's release! |
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.
Approved with minor comments. It may be helpful to also highlight the "Problem" Page since this is new. This can show all the problem at once instead of moving the cursor around.
![image](https://private-user-images.githubusercontent.com/18221871/409952938-5a4a909d-9c9b-418d-bd2c-d36de4170531.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxOTA0NzksIm5iZiI6MTczOTE5MDE3OSwicGF0aCI6Ii8xODIyMTg3MS80MDk5NTI5MzgtNWE0YTkwOWQtOWM5Yi00MThkLWJkMmMtZDM2ZGU0MTcwNTMxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDEyMjI1OVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPThkZTAxOTIyMzI5MjU2OGI0M2U5Y2E5NWE3OWU2ZDVkNmEwYTZmZTVkMDEzNjI5MzMwNWQwNDg1Y2U2YWVlNjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.WC7LGIRbUTd_4aM2LybZZSUHb12u9pqyKkJYCIlvVjs)
In additional, do we want to add some mention to this in Kedro's doc? We only have a page for [Setup VSCode], but maybe this is something we want to highlight.
Yep indeed, an update to our docs is due. I'll open an issue about it. |
@noklam Sorry I did not get it completely, where we need to highlight ? are you suggesting to make this changes in this PR ? |
@jitu5 I mean the README as I saw the GIF is replaced. ![]() ^ok it's actually on the same page so I guess there is no change on the "Problem Page", for some reason I thought it's a new tab. |
This pull request includes updates to the Kedro VSCode Extension, with changes to the changelog, version number, and dependencies. The most important changes include adding new features, updating the version, and modifying the requirements for testing.
Major changes and new features:
#162: Support settings of custom project path in Kedro Extension.
#163: Enable primary tool bar with toolbarOptions.
#159: Validate dataset classes in catalog using LSP.
#164: Remove the old dependencies with yaml schema.
Version update:
0.2.3
to0.3.0
inpackage.json
.