Repository navigation
chore: update changelog and release - #220
Merged
Merged
Conversation
|
Note The title starts with
|
wolfstarbot
force-pushed
the
changeset-release/main
branch
from
October 6, 2026 12:08
1ed0ce5 to
a20e6f7
Compare
@wolfstar/plugin-api
@wolfstar/plugin-broker
@wolfstar/plugin-cache
@wolfstar/plugin-gateway
@wolfstar/plugin-i18next
@wolfstar/plugin-logger
@wolfstar/plugin-scheduled-tasks
@wolfstar/plugin-sharder
@wolfstar/plugin-subcommands-advanced
commit: |
wolfstarbot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
October 6, 2026 16:48
49fd104 to
a09ec7e
Compare
wolfstarbot
force-pushed
the
changeset-release/main
branch
from
October 7, 2026 13:01
a09ec7e to
ce1d6c0
Compare
wolfstarbot
force-pushed
the
changeset-release/main
branch
from
October 7, 2026 16:11
ce1d6c0 to
79582ee
Compare
RedStar071
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@wolfstar/plugin-cache@0.7.0
Minor Changes
4748f09- Cache the status and start time of voice channels:VOICE_CHANNEL_STATUS_UPDATE,VOICE_CHANNEL_START_TIME_UPDATEandCHANNEL_INFOpatch thestatusandvoice_start_timeof a cached channel, and leave an uncached one uncached.@wolfstar/plugin-gateway@0.12.0
Minor Changes
#222
ff72647- Addcategory.childrenandanswer.votersto@wolfstar/plugin-gateway, after discord.js.category.childrenis aCategoryChannelChildManager: itscachelists the cached channels of the category (a promise with an asynchronous cache),create()makes a channel inside it, andresolve()/resolveId()look one up.answer.votersis aPollAnswerVoterManagerwhosefetch()lists the users who voted for the answer;fetchVoters()now goes through it.Unlike discord.js,
children.cacheis read from the channel store on each access, so a store that cannot enumerate its entries throwsCacheNotIterable, andcreate()rejects a category as the channel type.answer.votershas nocache.#226
9eff0b0- AddGuildManager#fetchSoundboardSounds(guildIds, options?)to@wolfstar/plugin-gateway, which requests the soundboard sounds of several guilds over the gateway (opcode 31) like discord.js, caches them, and resolves with aCollectionof each guild's sounds. It sends one request per shard and waits for theSOUNDBOARD_SOUNDSreply of every guild, rejecting with the newGuildSoundboardSoundsTimeoutError(listing the guilds still missing) when they take longer thantime(10 seconds by default, restarted by each reply).The replies carry no nonce, so only the process that sent the request resolves it, and a reply arriving after the timeout is only cached.
#221
3a209a4- Add small manager methods of discord.js to@wolfstar/plugin-gateway:DataManager#valueOf()(the manager's cache),GuildEmojiManager#resolveIdentifier(),GuildManager#widgetImageURL(guild, style?)andGuildChannelManager#channelCountWithoutThreads.Unlike discord.js,
resolveIdentifierthrows for a value it cannot resolve instead of returningnull(an uncached emoji ID still answersnull), andchannelCountWithoutThreadsthrowsCacheNotIterablewhen the channel store cannot enumerate its entries.#223
4748f09- Add the status and start time of voice channels to@wolfstar/plugin-gateway, after discord.js.VoiceChannelgetsstatus,voiceStartTimestampandvoiceStartAt(allnulluntil Discord sends them) andsetStatus(). The newvoiceChannelStatusUpdateandvoiceChannelStartTimeUpdateevents carry the channel before and after, andclient.channels.requestInfo()(alsoguild.requestChannelInfo()) asks a guild's shard for the info over the gateway, resolving once thechannelInforeply is cached or rejecting with aGuildChannelInfoTimeoutError.Requests for one guild run one after the other, because Discord's reply has no nonce, and only the process that sent a request resolves it. A
GUILD_CREATEresets both fields tonull.#219
3954f0f- Add the managers of a guild, whose cache is keyed by the entity's ID alone, like discord.js:guild.members,guild.roles,guild.voiceStatesandguild.presences, also reachable asclient.guilds.members(guildId),roles(guildId),voiceStates(guildId)andpresences(guildId).guild.members.cache.get(userId)replacesclient.members.cache.get(client.members.resolveKey(guildId, userId)), which keeps working. Each manager has the methods of the client's one with the guild's ID filled in (guild.members.kick(userId),guild.roles.create(options), ...), andchannel.messagesandthread.membersgain the samecache.guild.members.meis a getter, like discord.js's. They are the client's managers themselves, built with a guild's ID as an optional second argument and typedGuildMemberManager<true>,RoleManager<true>,VoiceStateManager<true>andPresenceManager<true>: the classes gain anInGuildtype parameter (falseby default, so existing code is unaffected) and aguildIdproperty. On the client's managermeis now a property holding the function rather than a prototype method, called the same way (client.members.me(guildId)).Patch Changes
cd3dcda- FixGatewayClientnever becoming ready when its shards resume a stored session (sessionStore). A shard that resumes getsRESUMEDand noREADY, soclientReadywas never emitted,isClientReady()stayedfalseandclient.userstayednull. The client now restoresclient.userfrom the cache, or fromGET /users/@mewhen the cache does not hold it, and emitsclientReadyonce every shard is ready, whether it got there throughREADYorRESUMED. A failed restore is reported througherrorand does not holdclientReadyback.4748f09]:@wolfstar/plugin-scheduled-tasks@0.2.0
Minor Changes
1ba434b- Add a readiness gate for tasks that need the app to be up. Give the plugin areadycallback (with optionalreadyTimeoutandreadyDelay) and setwaitForReady: trueon the tasks that need it: when a job is taken before the app is ready it waits, and if the timeout passes it is moved back todelayedinstead of failed, so it costs no attempt and emits noscheduledTaskError. The newscheduledTaskNotReadyevent (ScheduledTaskEvents.ScheduledTaskNotReady) reports it, andScheduledTaskHandler#waitForReady()lets a task wait by hand.ScheduledTaskHandler#runtakes an optional second argument with the BullMQ job and token.@wolfstar/plugin-broker@0.5.1
Patch Changes
4748f09]: