Release all affected packages?

🐛 Bug Report

Multiple react-aria packages are falling behind versions so you can’t really use multiple react-aria packages together

🤔 Expected Behavior

All affected packages to be released when an internal package dependency is updated.

😯 Current Behavior

Internal packages are pointing to old versions of other internal packages.

💁 Possible Solution

Publish new versions of all packages that are affected by a code change made to internal packages. Maybe implementing semantic-release and multi-semantic-release?

🔦 Context

Building my own design system using react-aria packages and connecting them all together.

💻 Code Sample

Example number 1:

import React, { useCallback, useRef } from "react";
import { useButton } from "@react-aria/button";
import type { PressEvent } from "@react-types/shared";


export default function App() {
  const buttonRef = useRef<HTMLButtonElement>(null);
  const onPress = useCallback<(e: PressEvent) => void>((e) => {
    console.log(e)
  }, []);
  const { buttonProps } = useButton(
    {
      onPress,
      type: 'button'
    },
    buttonRef
  );
  return (
    <button {...buttonProps}>Click Me</button>
  );
}

typescript complains about onPress type not being the same

🌍 Your Environment

Software	Version(s)
@react-types/shared	3.10.0
@react-aria/button	3.3.4
Browser	Doesn’t matter
Operating System	Doesn’t matter

[devongovett]

Yeah sometimes I manually bump every package because it’s easier than figuring out the minimal set of changes.

I think the current behavior is “correct”, but I can understand that it is confusing to deal with lock files. Perhaps we can improve something here.

[justsaul]

Are there any plans to fix it? I can’t really get behind that regenerating lock files is considered as a correct solution when it’s publishing issue.