Hi @gregwhitworth , in June 2023 you were announcing great news about Lightning Base Components https://t.co/kpWV5unVbw
A year later, we discover that "This package has been deprecated, publishing of the package has been paused".
What's the whole story ?
@ch_sz_knapp@salesforcedocs I'm also interested in knowing what's going on here. The docs for v61.0 Summer 24 still show "Reserved for internal use. Do not use this object."
Open Letter to Tim Cook: Sabotaging Web Apps is Indefensible
๐จ Apple breaking EU Web Apps in < 7 days
๐ข Many companies will be bankrupted / severely hurt
๐ This does global damage to the web
๐SIGN THE OPEN LETTER (Link below)
@ch_sz_knapp@AlbaSFDC The same `retrieve()` call of the Metadata API behaves differently depending on whether the org has Source Tracking enabled or not.
I documented this 2 years ago when I noticed it: https://t.co/PKH41q7sgM
@altius_rup@SalesforceDevs@MShaneMc Yes, you can change the description of an Outbound Changeset without re-deploying the actual metadata by simply omitting the components from the package.xml:
@altius_rup@SalesforceDevs@FabienTaillon Is it really optional? Let's say you expect either a default org or --target-org flag, then I'd say the flag is required.
We are huge believers in the power of packaging. That is why we have launched a brand-new Packaging Module! It visualizes your second-generation packages and supports installing them from a user-friendly UI. ๐ฅณ๐๐ป
#secondgenerationpackaging#salesforce
https://t.co/P4LEM9JGk1