FluidFramework/feeds
Jason Hartman 42b323cdbf
build(client): publish experimental presence (#22499)
+ Note current Notifications limitation
+ Connect docs to readme with more details
2024-09-16 11:47:41 -07:00
..
README.md build: Add per-feed package lists to aid reviews (#17634) 2023-10-05 13:23:54 -07:00
internal-build.txt build(client): publish experimental presence (#22499) 2024-09-16 11:47:41 -07:00
internal-dev.txt Add mocha-test-setup to published packages (#20204) 2024-03-19 12:54:05 -07:00
internal-test.txt build(client): publish experimental presence (#22499) 2024-09-16 11:47:41 -07:00
public.txt build(client): publish experimental presence (#22499) 2024-09-16 11:47:41 -07:00

README.md

The files in this folder are lists of packages that should be published to the four npm feeds that we publish to. They provide an "audit" of what should go where.

As we add/remove/move packages, these lists will change and we use them to verify before we run the publishing pipeline what will be published. The CI pipeline just publishes the packages in each list to the feed in question. This makes it far less likely that we find out a package is missing in a feed only after we do a release.

They are generated by running the generate:packageList script from the root of the release group. They are also generated during a build, so these files are kept up-to-date as changes are made.