New command: spo file version keep. Closes #6774

[Saurabh7019]

Closes #6774

[milanholemans]

Thanks, we'll try to review it ASAP!

[milanholemans]

Nice work @Saurabh7019, I think we're almost ready to merge it with a few tiny changes.

[milanholemans]

Additionally, for new commands, we now also require a section called Permissions for the docs page where we list the minimal permissions needed to run this command. Could you add it to this page as well, please?

More info: https://pnp.github.io/cli-microsoft365/contribute/new-command/writing-the-docs#permissions
Examples: any planner command.

Thanks!

[Saurabh7019]

there's a minor issue in the above. the command has an extra -- . The correct usage is npm run devproxy:permissions -- -e "tenant=contoso"

Should we fix it as part of this issue?

[milanholemans]

@Saurabh7019, are you using PowerShell? If I'm not mistaken, you should use -- -- over there.
Edit: just tested it, seems to be working for me in PowerShell. Make sure that you select the right shell in the docs, for other shell it's a single -- indeed.

[Saurabh7019]

@Saurabh7019, are you using PowerShell? If I'm not mistaken, you should use -- -- over there. Edit: just tested it, seems to be working for me in PowerShell. Make sure that you select the right shell in the docs, for other shell it's a single -- indeed.

@milanholemans, Thanks for checking. let's ignore this if it's not an issue for others. I just thought it might be a typo.

I am using PowerShell, but it isn't working for me.

[milanholemans]

@Saurabh7019, are you using PowerShell? If I'm not mistaken, you should use -- -- over there. Edit: just tested it, seems to be working for me in PowerShell. Make sure that you select the right shell in the docs, for other shell it's a single -- indeed.

@milanholemans, Thanks for checking. let's ignore this if it's not an issue for others. I just thought it might be a typo.

I am using PowerShell, but it isn't working for me.

I'm using PowerShell as well, and it seems to be working from my side:

You can always create a new issue with the issue you are observing so we can find out what is causing this.