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.

Sign up for GitHub

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

Jump to bottom

❗❗📢 Removal of support of TFS 2017 and 2018 with VSTeam version 8.0.0 #438

Open
SebastianSchuetze opened this issue Jan 12, 2022 · 2 comments · May be fixed by #458
Open

❗❗📢 Removal of support of TFS 2017 and 2018 with VSTeam version 8.0.0 #438

SebastianSchuetze opened this issue Jan 12, 2022 · 2 comments · May be fixed by #458
Assignees
@SebastianSchuetze

Comments

@SebastianSchuetze
Copy link
Collaborator

SebastianSchuetze commented Jan 12, 2022 •
edited
Loading

The plan is the remove support TFS 2017 and 2018. We have no possibility to test this and is cluttering the code base. This is getting harder to manage.

With older version VSTeam can still be used or by setting the VSTeam API manually or using Invoke-VSTeamRequest.

It's not set yet when this will happen (few months probably). I will add a warning message with the next release that will be shown when the module is loaded.
@SebastianSchuetze SebastianSchuetze pinned this issue Jan 12, 2022
@SebastianSchuetze SebastianSchuetze changed the title Removal of support of TFS 2017 and 2018 with VSTeam version 8.0.0 ❗❗📢 Removal of support of TFS 2017 and 2018 with VSTeam version 8.0.0 Jan 12, 2022
@SebastianSchuetze SebastianSchuetze mentioned this issue Jan 12, 2022
Merged
@SebastianSchuetze SebastianSchuetze linked a pull request Feb 1, 2022 that will close this issue
Added breaking change warning and new version notification on module load #440
Merged
@SebastianSchuetze SebastianSchuetze removed a link to a pull request Feb 1, 2022
Added breaking change warning and new version notification on module load #440
Merged
@SebastianSchuetze SebastianSchuetze self-assigned this Feb 28, 2022
@SebastianSchuetze SebastianSchuetze linked a pull request Feb 28, 2022 that will close this issue
BREAKING CHANGE: Removing support for AzDO Version 2018 and earlier #458
Draft
@SebastianSchuetze
Copy link
Collaborator Author

I am starting to work on this and will be merged an extra branch for Version 8.0.0 until everything is ready.

@okamilobo
Copy link

@SebastianSchuetze we started seeing this warning, but are having trouble figuring out is causing us to get the warning. Could you please elaborate on what we should be looking for in our code and what to upgrade to?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SebastianSchuetze SebastianSchuetze

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

BREAKING CHANGE: Removing support for AzDO Version 2018 and earlier MethodsAndPractices/vsteam
2 participants
@SebastianSchuetze @okamilobo