component stays staged even after exported

[KutnerBitsrc]

web git/master*  
❯ bit tag iframe/communicator --minor
⡀⠀ importing components(node:62958) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
2 component(s) tagged
(use "bit export [collection]" to push these components to a remote")
(use "bit untag" to unstage versions)

changed components
(components that got a version bump)
     > bit.capsule/iframe/communicator@0.3.0
       auto-tagged dependents: bit.capsule/playground-client@0.0.5

web git/master*  
❯ bit export bit.capsule iframe/communicator
exported 1 components to scope bit.capsule

web git/master*  6s
❯ bit s                                     
modified components
(use "bit tag --all [version]" to lock a version with all your changes)
(use "bit diff" to compare changes)

     > playground-client ... ok
                         

staged components
(use "bit export <remote_scope> to push these components to a remote scope")

     > iframe/communicator. versions: 0.3.0 ... ok
     > playground-client. versions: 0.0.5 ... ok

it is super weird, I can't find any place that references iframe/communicator (not even in .bitmap)
Only cause I can think of is upgrading to bit 14.3.0.
Could this be a bug in the new version?

[davidfirst]

@KutnerBitsrc , yes, that's probably related to the new v14.3.0 version.
We added a new feature that enables users to export to a different scope and leave the local workspace untouched. So, later on, it'll easy to export to the default scope.

In other words, if you exported this component to one scope, and bit.capsule is another scope, it is by design. If bit.capsule is the same scope you exported before, it is a bug, and it'd be great to get a zip file of your workspace so I could reproduce it.

[GiladShoham]

I talked with @KutnerUri and he said it was the same scope. so it's probably a bug.

[KutnerBitsrc]

when I think about it again, the component had an older copy under the 'bitsrc' user. I don't remember changing collection, but it is possible.

ok then, how to resolve tagged component that has been exported to another scope?
we should at least reflect this to the user

[davidfirst]

@KutnerBitsrc , you can use --set-current-scope flag to preserve the previous behavior.
I can see why users would be surprised by this new feature. @itaymendel , any suggestion here?

[KutnerBitsrc]

thanks for the info

[KutnerBitsrc]

getting the same error again, staying stuck on nothing to export.
how to use --set-current-scope ?

[davidfirst]

That's strange. When it's staged you supposed to be able to export it. Unless it's already exported to that scope.
--use-current-scope is a flag of bit export. (so, just run bit export [remote] --use-current-scope).

Again, if it's possible to send a reproducible file, it'd be a great help.

[KutnerBitsrc]

sorry, I already did bit init --hard-reset after backuping the bit.json and reimported local components. It's a bitter solution but it worked.

[davidfirst]

As part of #2004, a new confirmation message has been added before exporting to a new scope.
This message also warns about components staying as staged when --set-current-remote was not used.
Implemented on #2012.