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

Prepare v3 pre-release #2648

Merged
merged 3 commits into from
Jan 12, 2024
Merged

Prepare v3 pre-release #2648

merged 3 commits into from
Jan 12, 2024

Conversation

JillieBeanSim
Copy link
Contributor

@JillieBeanSim JillieBeanSim commented Jan 4, 2024

Proposed changes

Update version for pre-release 3.0.0-next.202401041628

Release Notes

Milestone: vNext

Changelog: n/a

Types of changes

What types of changes does your code introduce to Zowe Explorer?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Updates to Documentation or Tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This checklist will be used as reference for both the contributor and the reviewer

  • I have read the CONTRIBUTOR GUIDANCE wiki
  • PR title follows Conventional Commits Guidelines
  • PR Description is included
  • gif or screenshot is included if visual changes are made
  • yarn workspace vscode-extension-for-zowe vscode:prepublish has been executed
  • All checks have passed (DCO, Jenkins and Code Coverage)
  • I have added unit test and it is passing
  • I have added integration test and it is passing
  • There is coverage for the code that I have added
  • I have tested it manually and there are no regressions found
  • I have added necessary documentation (if appropriate)
  • Any PR dependencies have been merged and published (if appropriate)

Further comments

@JillieBeanSim JillieBeanSim added v3 no-changelog Add to PR's that don't require a CHANGELOG update labels Jan 4, 2024
@JillieBeanSim JillieBeanSim added this to the v3 pre-releases milestone Jan 4, 2024
@JillieBeanSim JillieBeanSim self-assigned this Jan 4, 2024
Copy link

codecov bot commented Jan 4, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (75e848f) 93.42% compared to head (72dcc54) 93.42%.

Additional details and impacted files
@@           Coverage Diff           @@
##             next    #2648   +/-   ##
=======================================
  Coverage   93.42%   93.42%           
=======================================
  Files         109      109           
  Lines       10237    10237           
  Branches     2134     2134           
=======================================
  Hits         9564     9564           
  Misses        672      672           
  Partials        1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

zFernand0
zFernand0 previously approved these changes Jan 5, 2024
Copy link
Member

@zFernand0 zFernand0 left a comment

Choose a reason for hiding this comment

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

LGTM! 😋
Should we remove the Theia workflow form the next branch?

@JillieBeanSim
Copy link
Contributor Author

I created an issue other day for removing Theia checks and accompanying code
#2647

zFernand0
zFernand0 previously approved these changes Jan 8, 2024
@zFernand0
Copy link
Member

I created an issue other day for removing Theia checks and accompanying code #2647

Thanks for removing the workflow. And yes, we can target all other code changes around dropping Theia support in that issue 😋

@JillieBeanSim JillieBeanSim marked this pull request as draft January 8, 2024 14:36
@JillieBeanSim
Copy link
Contributor Author

I see an issue on next branch with the Issue Unix command with following error via USS treeview. Will investigate
Screenshot 2024-01-08 at 9 36 06 AM

@JillieBeanSim
Copy link
Contributor Author

also this during startup of extension
Screenshot 2024-01-08 at 9 38 33 AM

@zFernand0
Copy link
Member

zFernand0 commented Jan 8, 2024

I see an issue on next branch with the Issue Unix command with following error via USS treeview. Will investigate Screenshot 2024-01-08 at 9 36 06 AM

hey @JillieBeanSim,
I noted this behavior in the following issue:

I didn't see it as a showstopper (for the PR that introduced multi-ssh profile support)

@zFernand0
Copy link
Member

also this during startup of extension Screenshot 2024-01-08 at 9 38 33 AM

oh, and this one might be related to...

@JillieBeanSim
Copy link
Contributor Author

JillieBeanSim commented Jan 9, 2024

also this during startup of extension Screenshot 2024-01-08 at 9 38 33 AM

oh, and this one might be related to...

I think something went wrong with merge from main for the command error on start up since this isn't experienced with main.
The other was due to a token in base and trying to share with ssh profile after looking into it

Signed-off-by: Billie Simmons <[email protected]>
@JillieBeanSim
Copy link
Contributor Author

the command was in the "view/item/context" array but not in the "command" array of package.json where they are initially created and also not registered during activation. It also doesn't exist on main branch, so removing.

@JillieBeanSim JillieBeanSim marked this pull request as ready for review January 9, 2024 14:34
Copy link

sonarcloud bot commented Jan 9, 2024

Quality Gate Passed Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@zFernand0
Copy link
Member

Hey @JillieBeanSim,
Thanks for looking into this and fixing it! 🥳


Regarding:

I think something went wrong with merge from main

@traeok, @t1m0thyj, do you think that fewer of these cases will occur if the improvements to the deployment workflow (that you guys brought up) were rolled out?

Copy link
Member

@t1m0thyj t1m0thyj left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @JillieBeanSim!

@@ -1405,11 +1405,6 @@
"command": "zowe.jobs.editSession",
"group": "099_zowe_jobsProfileModification@0"
},
{
"when": "view == zowe.jobs.explorer && viewItem =~ /^(?!.*_fav.*)server.*/",
"command": "zowe.jobs.removeJobsSession",
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this menu item was referencing a non-existent command, so makes sense to remove it 👍

@traeok
Copy link
Member

traeok commented Jan 12, 2024

@traeok, @t1m0thyj, do you think that fewer of these cases will occur if the improvements to the deployment workflow (that you guys brought up) were rolled out?

Yep, this would minimize the amount of commits in merge PRs since next would be based on main (once v3 is GA)

Copy link
Member

@traeok traeok left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @JillieBeanSim 😁

@JillieBeanSim
Copy link
Contributor Author

Thanks @t1m0thyj & @traeok for reviewing so quickly

@JillieBeanSim JillieBeanSim merged commit 1556789 into next Jan 12, 2024
20 checks passed
@JillieBeanSim JillieBeanSim deleted the publish/3.0.0-next-prerelease branch January 12, 2024 17:46
Copy link

Release succeeded for the next branch. 🎉

The following packages have been published:

Powered by Octorelease 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-changelog Add to PR's that don't require a CHANGELOG update released v3
Projects
Status: Closed
Development

Successfully merging this pull request may close these issues.

4 participants